Leaderboard

As some folks are aware, back in Q4 of 2021, there was a massive breakage of many browsers due to some JavaScript changes that took place around then which rendered browsers that weren't the latest version of Chromium or Firefox useless on many sites. I myself have been struggling with this for some time; Iron 70 no longer works on many things and New Moon is almost the same way. Some things don't work in either, or one or the other. I eventually realized that as it was just JavaScript code on these sites that had been changed (in many cases, in libraries not directly part of the site, probably why this sprang up everywhere all in a short period of time), and that if that was the case, maybe there was a way to restore compatibility... I played around for a while this week, and at last, I have made some satisfying progress. StackOverflow and other StackExchange sites, which have been basically 70% broken (minimal functionality mode) for weeks now, finally work 100% again in Iron 70! All it took was minimal polyfill injecting before page load using a simple extension that I set up to do the trick. It looks like many of the other errors I'm seeing are caused by one other popular error. I'm going to see if that can be polyfilled in a similar way too. Right now, I'm tentatively calling it "Old Chrome Compatability"... couldn't really come up with any clever names, but that's basically the idea. Plan is to hopefully add that other thing and then open source it this week so that anybody can add it and use it. Granted, Chromium is probably less popular here than UXP browsers, maybe rightly so. Gets me to thinking, now that I know this concept works, maybe we can rig together a similar extension for Pale/New Moon. It might even be simpler there, the way it's set up. The polyfills needed for one won't necessarily apply to the other, but there'll probably be a fair bit of crossover. Any thoughts? Anyways, these id*** had their fun messing up their JavaScript to break all our stuff, but I'm taking my JavaScript back now... take that, Google...

All right, available now! https://blog.interlinked.us/66/when-the-world-wide-web-goes-on-strike-how-do-you-fight-back https://github.com/InterLinked1/chromefill Hands are a bit tied at the moment, but might try to see what will work for New Moon as well.. for now, this unbreaks enough sites on Iron 70 that it's usable enough again.

Yeah , about that . I 've come across this one also . This is an installer , right ? So you just need to place that stupid file right in it's folder . Sorry , lost the link. Oh , here it is , found it again ! https://github.com/nalexandru/api-ms-win-core-path-HACK

It's just a pref, so once you set it, it sticks even when you update New Moon. I can see the argument for turning it off by default (don't let NM ping the MCP server and poke the bear, so to speak), but some folks prefer NM to have the same default prefs as PM - fewer surprises that way - and it can always be turned off easily if desired.

Hello to all. First thanks all for your help! I've examined what was going wrong in my system. I found out that the patch in Restore_WU_XP_2003.7z didn't work in my system due to system file protection. The file wuaueng.dll was replaced by sfc. So I patched my sfc_os.dll in folder system32 to disable sfc. Here is a working instruction: After that patching I put the patched sfc_os.dll in both folder system32 and system32\dllcache. Now I was able to copy manually wuaueng.dll in both folders. But that was not enough. To get Microsoft Update working you have to edit config.ini in ProxHTTPSProxy or HTTPSProxy shown in my screenshot. Now it works and I can use Microsoft Update in my Internet Explorer. See my screenshot! https://imgur.com/CmN76Au https://imgur.com/re8X4cH

This thread is now locked. These types of arguments will never be resolved, and MSFN isn't the place for them, even in this section.

As you can see in my screenshot, I use ηMatrix in combination with uBlock-for-firefox-legacy. ηMatrix has some learning curve however, but has more fine-grained control than NoScript. (offtopic) Thanks for your Ffmpeg builds for XP!

ah yeah that is Palememe drama where Tobin decided to block Noscript for some personal reason. Noscript is fine. Reason it "breaks sites" is because it block JavaScript by default. Absolutely ridiculous reason to hard block it. Overall addon blocking is stupid idea, you give someone else control over what addons are ok and what are not. Go to settings>security and set addon security off. I wonder why@roytam1 left it on build since it keep pinging palememe servers. Could it be removed on future builds?