Leaderboard

Slight correction: Vista+ only, for quite some time now ... https://github.com/Eclipse-Community/r3dfox

I've made the uBO-legacy custom filter even more generic, because I've come across Discourse-based forums where the browser detecting script wasn't served from within an "assets" subfolder ; so, the version I'm currently using is: ! Discourse-based forums ||*/browser-detect-$script,important The now broken userscript just told Discourse's browser-feature-detection script that "CSS aspect-ratio (Fx-89+)" IS supported in UXP-based browsers; maybe Discourse are now looking for something new entirely or, besides CSS aspect-ratio, for additional (recent) features that the userscript (and, alas, UXP) doesn't support... A very savvy person would have to dissect the new version of Discourse's script, identify what new things they search for now and author a new userscript... Discourse, in March, issued the following announcement: https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131 so it's probably one or more of the new requirements there that broke things; FWIW, relative color syntax & subgrid aren't supported in UXP, probably the same applies to import-maps ... Recent upstream forum thread about Discourse's shenanigans : https://forum.palemoon.org/viewtopic.php?f=70&t=32600 Last post there is from Aug 13th, though...

Wow, ublock filter work for me (new moon current version), userscript - no, thanks.

They needed this user script: https://msfn.org/board/topic/184051-my-browser-builds-part-4/page/203/#findComment-1258499 but until yesterday they worked just fine with it. Maybe there is another (new) userscript needed. Will try supermium.

Different builds exist based on the capacities/age of the processor (CPU) on the machine the browser build is to be launched; if your CPU is archaic and doesn't support the SSE instructions set, use the -ia32 variant (sometimes referred to as "-nosse"); if your CPU is somewhat newer and does support SSE (but not SSE2), use the -sse variant; if your CPU does support SSE2 (and later), then you should use the "normal" build, whose filename ends in just "-xpmod.7z"... PS: Not relevant for XP users, but if you're on Win7+ x64 OS and want to use roytam1's NM28_x64 fork (you may have your reasons ), there's a fourth (64-bit, only) build variant that's meant for CPUs supporting AVX2 ; filename ending in "-w7plus-avx2.7z"... So, now you know ...

... That post is quite old by now ; the UXP-based browsers now are fully equipped with all the necessary plumbing (JS features) to fully support discoursed-based forums (their "full" version, not the "dumbed-down" one targeting unsupported browsers); however, their browser-detection scripts fail to recognise UXP-based browsers as "supported", so those sites offer to them that "simplified" version ... Some weeks ago, I had answered that same question posed by j7n but he didn't opt to apply my suggested solution, because it involves an adblocker extension (uBlock Origin legacy) and he did not want to install it himself, because a) he had already other arrangements in place to thwart ads b) he feared that installing that adblocker would, somehow, compromise the quality/speed of his browsing... Here at MSFN we are a democratic community, so I respect his reservations ; this doesn't mean others are discouraged from acting differently ... If one has already installed uBO, a custom filter can be added to block the script discourse-based forums serve to sniff browsers: ! Discourse-based forums ||*/assets/browser-detect-$script,important That should be added in the "My Filters" tab... OTOH, if you have a userscript manager installed (usually their names end in "*monkey" ), you can add a custom userscript like the one below: // ==UserScript== // @name CSS aspect-ratio [88] - Discourse Forums // @version 0.0.1 // @match *://*/* // @run-at document-start // @grant none // ==/UserScript== !function() { let CSS_supports = CSS.supports; CSS.supports = function(a) { return a === "aspect-ratio: 1" || CSS_supports(a); } }() This userscript doesn't block the browser-detecting script, it simply tells it that the feature it's looking for exists in the browser (it doesn't, as of now, in reality, but it isn't needed either for properly displaying those sites) ... So, @adata, you're being offered two current solutions for properly displaying and using ALL the discourse-based forums (not just the three you referenced in your post ) ... Best regards ! EDIT: If you're NOT running a recent version of Serpent 52, please DO update, preferably to this weekend's release!