Leaderboard

No firsthand experience. Supermium was never very stable on my computers. But as @jumper pointed out, I'm pretty sure that the developer already provides rebased .dll's. Haven't visited that GitHub project in a very long time so no clue where they are located. I've actually erased/deleted/permanently-moved-on from all of my XP "experiments", be they Supermium, Thorium, Pale Moon, New Moon, you name it, they ***ALL*** were nothing but "headaches". I obviously keep my own 360Chrome's around, but seldom are they ever launched. And the only Serpent that is reliable for my needs is a VERY OLD version - new updates only introduce new problems, nothing but "headaches".

Apologies again, but I'm afraid I'm not the person to ask. I ditched XP roughly a year or so ago and my life has IMPROVED a million-trillion-zillion times a million-trillion-zillion ever since! XP was holding me back !!! It's up to you to decide if all of the time spent to do things on XP is a waste of your time or not. Sorry. XP, to me, is like Linux, neat and novel, a good HOBBY, but nothing more than a HOBBY.

New build of post-deprecated Serpent/moebius for XP! * Notice: This repo will not be built on regular schedule, and changes are experimental as usual. ** Current moebius patch level should be on par with 52.9, but some security patches can not be applied/ported due to source milestone differences between versions. Test binary: Win32 https://o.rthost.win/basilisk/basilisk55-win32-git-20250719-3577496e0-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk55-win64-git-20250719-3577496e0-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - import from UXP: Issue #2499 - Part 1: Add overflow: clip support and tests (ad396c6c) (70c17fd4f) - import from UXP: Issue #2499 - Part 2: Fix overflow shorthand serialization for mixed clip values (205ea844) (ec17993dc) - import from UXP: Issue #2499 - Part 3: Add CSS clip overflow support with serialization fixes (5e8e1208) (68ce5c95d) - import from UXP: Issue #2720 - Follow-up: Use temp value for duplicate color stop (07cf2e64) (df0626865) - import from UXP: Issue #2736 - Follow-up: Stop using worker thread-only functions for checking if CSP is enabled (c8608ad5) (c9ee7fc5a) - import from UXP: Issue #2792 -Implements parsing, computed style, and writing mode mapping for overflow-block and overflow-inline properties (0903daca) (7194d6223) - import from UXP: Issue #2691: Implement ParseSupportsSelector (squashed) (3577496e0)

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20250719-3219d2d-uxp-198222fc03-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20250719-3219d2d-uxp-198222fc03-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20250719-3219d2d-uxp-198222fc03-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250719-d849524bd-uxp-198222fc03-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250719-d849524bd-uxp-198222fc03-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250719-d849524bd-uxp-198222fc03-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20250719-d849524bd-uxp-198222fc03-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20250719-d849524bd-uxp-198222fc03-w7plus-avx2.7z Official UXP changes picked since my last build: - Issue #2499 - Part 1: Add overflow: clip support and tests (ad396c6c59) - Issue #2499 - Part 2: Fix overflow shorthand serialization for mixed clip values (205ea844f4) - Issue #2499 - Part 3: Add CSS clip overflow support with serialization fixes (5e8e1208e7) - Issue #2720 - Follow-up: Use temp value for duplicate color stop (07cf2e643f) - Issue #2736 - Follow-up: Stop using worker thread-only functions for checking if CSP is enabled (c8608ad5cf) - Issue #2792 -Implements parsing, computed style, and writing mode mapping for overflow-block and overflow-inline properties (0903dacaa7) - Issue #2691: Implement ParseSupportsSelector (8be86514f0) - Issue #2691: Adjusted the function to use ParseSelectorGroup (e9a7190529) - Issue #2691: Add basic parentheses tracking to ParseSupportsSelector (fcb4b3d01f) - Issue #2691: Improve token handling for selectors (69556b7b1b) - Issue #2691: Enhance spacing logic for selector formatting (aaae6484ee) - Issue #2691: Add special handling for nth-child expressions (224d1724b2) - Issue #2691: Improve Parser State Handling (ea580ec54b) - Issue #2691: Refactored ParseSupportsSelector (f2d6170830) - Issue #2691: Utilize regex for spacing rules (906f05e606) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. Update Notice: - You may delete file named icudt*.dat inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

Apologies, but no. This rabbit hole is far too deep for me to get pulled in any further. Sorry. You will need to use Supermium and "let go" of the notion that a v86 Chrome engine can be made to do whatever you throw at it.

Your issue is with the developer.mozilla.org "test". findLastIndex does not require a polyfill in Chrome v97 and that "test" does not work in Chrome v97. It most likely does not work in v98, v99, v100, v101... et cetera... And doesn't "start to work" until who knows where. Again, Chrome v97 wholly and fully implements findLastIndex and even v97 cannot 'pass' that "test".

I have just copied my previously downloaded list from my installation with the version number 3.6.3.2. Therefore, this last version can't disappear.

Yep! This user has been blocked. Thanks for pointing to this issue! If this list doesn't appear anymore elsewhere, then I will have to remove this list from my release again, for better or worse.

Glad it works. I hadn't any problems when updating this filter list, though. When I am back at my Windows XP computer. I will have a look at this.

Hello @UCyborg! I have just tested your new release uBlock Origin 1.16.6b1 by using the ad block testing site https://test.adminforge.de/adblock.html. While my release uBlock Origin Legacy 1.16.4.34 blocked all ads with a score of 100%, your version wasn't able to do this and got a score of only 84%. The comparison was done using the same filter lists and same own filters in both versions. I was checking the performance of both releases with the uBO logger to see what's going on and noticed entries about noop.txt and noop.js in the log generated by your release which I didn't get when using my release. As far as I know, noop stands for no operation. One consequence of this is that some of my own filter rules under the tab "My rules" are simply ignored when using your release. Any ideas what your release is doing on this ad block testing site? Here is a screenshot testing uBlock Origin Legacy 1.16.4.34 in New Moon 28: And here is a screenshot testing uBlock Origin 1.16.6b in New Moon 28: Cheers, AstroSkipper

Update notification! - uBlock Origin Legacy 1.16.4.34 - Special mod by @AstroSkipper I have again updated my special mod uBlock Origin Legacy from version 1.16.4.33 to version 1.16.4.34. Starting with this version, installing over an existing installation of uBlock Origin Legacy (1.16.4.34 and higher) is completely working again. The immediate loading of the updated, internal list of all preselected filter lists (assets.json) can be triggered by the function "Purge all caches" or "Update now". From now on, the user will get the internal list of all preselected filter lists (assets.json) automatically. And I added new filter lists to different groups. More details can be found in the changelog in my main article, and of course the download link. The update to version 1.16.4.34 should be done as already described, but this time for the very last time. The easiest way is the alternative method: Backup all your settings using the "Back up to file" button on the page "Settings". Install the new version of uBlock Origin Legacy over the existing one. Reset your installation using the "Reset to default settings" button on the page "Settings". Restore all settings from your backup file. Cheers, AstroSkipper

I do know that CSS styling can also be done inside a JavaScript file. But separating the CSS code in a css file is the usual way when loading files from the chrome folder. Doing so the different CSS styles can be easily enabled or disabled and therefore managed by the userchrome.css file regardless of the script files.

You're welcome! This is what I understand by the term autoconfiguration: https://support.mozilla.org/en-US/kb/customizing-firefox-using-autoconfig My package MYPAL_68_CB_requirements.7z contains configuration files as the prerequisite for loading script and css files. Although these files are loaded automatically when starting the browser, the creators of these configuration files do not use the term autoconfiguration at this point. This is merely a question of defining the term.

First of all, I think it's right and good that someone other than myself is also working on the great and very important extension uBlock Origin Legacy and developing it further. Since nothing has happened for years, I see my efforts here in relation to uBlock Origin Legacy as a kind of initial spark to maintain this extension again and bring it up to date. Based on the way a well-known American moron speaks I would say: "Make uBlock Origin Legacy great again!" @UCyborg has started a promising project on GitHub. I already had a look at it. An indirect collaboration has already taken place, as he has used my internal list of all standard filter lists, i.e. the assets.json file, as the basis for his one. But I cannot and will not comment on direct collaboration at this point. In any case, I will continue to maintain my version here for a while. The next version is coming up very soon. This means that the user now has the option of choosing their preferred version. As I have already said between the lines, a wider range of products generally stimulates "business". Cheers, AstroSkipper

As far as I know, Serpent 52 gets more patches from the UXP branch than Serpent 55. The reason for that is not all of these patches can be applied to Serpent 55. Therefore, Serpent 52 is a bit more up-to-date. But @roytam1 and @VistaLover can tell more about that. And if I remember correctly, they already did that in @roytam1's browser threads in the past.

No, I do not use the property window.status. The script code for creating such a status bar has not grown out of my own hands, though. I simply took over an old script which is still working in Mypal 68. TBH, there are a couple of scripts but most of them are not compatible with Mypal 68. My part was finding working code. And that wasn't so easy due to the age of Firefox 68. Many scripts targeting this Firefox version have been lost or replaced by newer ones. However, I modified the css file for exact placing the status panel onto the status bar by myself. And the css file I am using is much more modified and exactly adapted to my browser, in which I also made changes to the interface font. This file is therefore useless for other users.