My Browser Builds (Part 6)

[NotHereToPlayGames]

Edited 2 hours ago by NotHereToPlayGames

[NotHereToPlayGames]

[VistaLover]

40 minutes ago, NotHereToPlayGames said:

It's because that page uses a ton of ":has()" .css declarations

... But the :has() CSS pseudo selector has been enabled by default since Fx-121 (release channel), while earlier implementations were behind a disabled about:config pref since Fx-103:

https://caniuse.com/css-has

Firefox is now at version 153.0.4; surely, one can't really blame website owners if the web frameworks they employ make use of :has() ? Even FxESR-115 (supported until March 2027) used on Win7/8/8.1 has the support easily accessible behind the "layout.css.has-selector.enabled" flag; as we've discussed multiple times in the past in these threads, the UXP platform remains oblivious to (practically) all of modern web designers, as backwards-compatibility isn't "a thing" anymore since many years already ; Mozilla use Stylo (or whatever it's called now) for Firefox's CSS features and this is unavailable to UXP devs, so I kind of feel for them ; hopefully, their first attempt at supporting :has() can be made a lot better (if indeed that's the major problem plaguing now GitHub pages, which I'm mostly concerned about ) ...

[NotHereToPlayGames]

23 hours ago, VistaLover said:

But when absolute disaster strikes is when one tries to access and load the Issues List view of a GH repository, say

https://github.com/violentmonkey/violentmonkey/issues

.css files are all over the place at github.

Instead of one very large .css, they seem to use dozens upon dozens of smaller .css files.

I only opened three of them and all three used the :has() declaration.

While I am not proclaiming the newly-implemented :has() is the root of all of these issues.

BUT...  it is the ONLY change implemented in the most recent weekly update.

So one really doesn't need to have to dig too deep into the change log to see just "what" is causing recent issues.

[Mathwiz]

19 minutes ago, VistaLover said:

But the :has() CSS pseudo selector has been enabled by default since Fx-121 (release channel), while earlier implementations were behind a disabled about:config pref since Fx-103:

Does UXP's new :has() support honor that same about:config pref? If so, disabling the pref might be a workaround for the serious performance issues with it.

[VistaLover]

14 minutes ago, Mathwiz said:

Does UXP's new :has() support honor that same about:config pref?

No...

[Mathwiz]

Well, it was a matter of the purest optimism to have posed the query in the first place....

Perhaps @roytam1 could implement the pref and use it to temporarily shut off :has() support, in the hope that an upstream fix will soon be available.