New whitehouse.gov rendering issues
Moderator: trava90
Forum rules
Please always mention the name/domain of the website in question in your topic title.
Please one website per topic thread (to help keep things organized). While behavior on different sites might at first glance seem similar, they are not necessarily caused by the same.
Please try to include any relevant output from the Toolkit Error Console or the Developer Tools Web Console using the following procedure:
Please always mention the name/domain of the website in question in your topic title.
Please one website per topic thread (to help keep things organized). While behavior on different sites might at first glance seem similar, they are not necessarily caused by the same.
Please try to include any relevant output from the Toolkit Error Console or the Developer Tools Web Console using the following procedure:
- Clear any current output
- Navigate or refresh the page in question
- Copy and paste Errors or seemingly relevant Warnings into a single [ code ] block.
-
datan2856
- New to the forum
- Posts: 1
- Joined: 2025-03-06, 09:45
New whitehouse.gov rendering issues
Hello there and nice to meet all of you here and I just want to say not political or anything but the new whitehouse.gov of the new admin has some serious css rendering issues which I do not have any problems on modern firefox or chrome? Maybe they are too lazy to code for older "outdated" web browsers also nowdays and it is a wordpress site I think...
You do not have the required permissions to view the files attached to this post.
-
Moonchild
- Pale Moon guru
- Posts: 37352
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
Re: New whitehouse.gov rendering issues
It's wordpress, yes. and it seems it's doing something very odd in one of the init modules:
I'm not even sure in what context that would make sense... trying to make/redefine something async after the fact? Is that valid JS? Feels like it isn't.
But, it throws an "await is a reserved identifier" error there, which would prevent their styling from working. Perhaps another case of Issue #2229 (UXP).
Code: Select all
s=await s;But, it throws an "await is a reserved identifier" error there, which would prevent their styling from working. Perhaps another case of Issue #2229 (UXP).
"The world will not be destroyed by those who do evil, but by those who watch them without doing anything." - Albert Einstein
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
-
adoxa
- Lunatic
- Posts: 381
- Joined: 2019-03-16, 13:26
- Location: Qld, Aus.
Re: New whitehouse.gov rendering issues
In addition to top-level await it also uses import maps and CSS clamp & aspect-ratio. Here's a Modify HTTP Response filter to work around them all (at least, for the front page, I didn't try anything else).
Code: Select all
[["www.whitehouse.gov",["/view-module\\.js/",[";s=await s",".then(a => s = a)","\"Swiper\"","\"https://www.whitehouse.gov/wp-content/themes/whitehouse/assets/js/modules/swiper.js?ver=6.7.2\""]],["/view\\.js/",["\"@wordpress/interactivity\"","\"https://www.whitehouse.gov/wp-includes/js/dist/script-modules/interactivity/index.min.js?ver=907ea3b2f317a78b7b9b\""]],["/style-index\\.css|^[^.]*$/",["/clamp\\(.*?,(.*?),.*?\\)/g","calc($1)","min-height:0;min-width:0","min-width:573px"]]]]