My Browser Builds (Part 3)

**VistaLover** · March 20, 2022

16 hours ago, VistaLover said:

Currently, the following hostnames are inaccessible:

aus.palemoon.org (checks for/delivers updates to official PM browser)
forum.palemoon.org (official PM/Bk user support forum, with tons of invaluable info accummulated over the years - much of it also applicable to the forks...)
addons-legacy.palemoon.org (extension repo for PM<=29.4.4)
addons.palemoon.org (extension repo for PM>=30.0.0)
rm-eu.palemoon.org (European CDN that delivers binary releases[installers, 7z packages, portables])
addons.basilisk-browser.org (extension repo for Basilisk)

8 hours ago, nicolaasjan said:

The forum is back online now.

However the add-ons site is still offline...

aus.palemoon.org
forum.palemoon.org
rm-eu.palemoon.org

are at this time BACK ; related:

https://forum.palemoon.org/viewtopic.php?f=1&p=225096

**nicolaasjan** · March 20, 2022

19 minutes ago, VistaLover said:

aus.palemoon.org
forum.palemoon.org
rm-eu.palemoon.org

are at this time BACK ; related:

https://forum.palemoon.org/viewtopic.php?f=1&p=225096

I wonder how MC will be able to bring the add-on site back.

It think it was on a server owned by MAT... :realmad:

Fortunately I saved all xpi updates earlier for use in my various VM's. :cool:

**InterLinked** · March 20, 2022

1 minute ago, nicolaasjan said:

I wonder how MC will be able to bring the add-on site back.

It think it was on a server owned by MAT...

Fortunately I saved all xpi updates earlier for use in my various VM's.

Call me paranoid, but this is why I keep copies of installers for things, just so I can be sure about them

I only have XPI files for the few extensions in New Moon, Mail News, etc. that I'm actually using, but I guess it's good that "they're there", now...

**Sampei.Nihira** · March 20, 2022

MC got what he fully deserved.

**nicolaasjan** · March 20, 2022

(offtopic)

@VistaLover

Can you have a look at my issue here:

https://msfn.org/board/topic/183247-python-3615-for-windows-xp-sp3/#comment-1211582

**nicolaasjan** · March 20, 2022

MC explains the ordeal further here:

https://forum.palemoon.org/viewtopic.php?f=65&t=28003&start=20#p225174

**UCyborg** · March 20, 2022

On 3/18/2022 at 2:28 AM, VistaLover said:

https://github.com/martok/palefill

Does anyone here understand how are you supposed to use this? GitHub works, but what about other random sites requiring customElements? I still get the same old error about being undefined.

Are you supposed to modify the extension itself to add rules?? I thought this was supposed to work generally, surely description says "Inject Polyfills for various web technologies into pages requiring them".

**VistaLover** · March 20, 2022

5 hours ago, UCyborg said:

but what about other random sites requiring customElements? I still get the same old error about being undefined.

Are you supposed to modify the extension itself to add rules?? I thought this was supposed to work generally, surely description says "Inject Polyfills for various web technologies into pages requiring them".

That extension started originally as a github-wc-polyfill fork , i.e. ONLY supporting initially GitHub/GitLab; unlike the upstream maintainer (JustOff) not wanting to support other sites beyond those two, the German maintainer (martok) of this fork will accept support requests for other sites broken in current UXP and will explore the possibility/feasibility of applying the necessary polyfills (where available) to address the breakage on those requested sites...

At this very moment, the only additional (to GH/GL) site supported is "godbolt.org", while a request for "*.notion.*" URIs is still pending (but supposedly very difficult to materialise) ...

https://github.com/martok/palefill/issues?q=is%3Aissue+sort%3Aupdated-desc+is%3Aopen
( ... of this "open issues" group, #3 and #6 aim to add user-side configuration options )

https://github.com/martok/palefill/issues?q=is%3Aissue+sort%3Aupdated-desc+is%3Aclosed

Edited March 20, 2022 by VistaLover

**DanR20** · March 20, 2022

6 hours ago, VistaLover said:

... probably because MCP had less time to move things around and worsen the performance levels attained originally by Mozilla ...

What you can still do is use St55 for everything besides GitHub/GitLab and for these two "villains" use a minimal fresh St52 profile with just uBO+gh-wc-pf extensions...

That most likely explains it. Currently I'm only running into problems with 4 or 5 sites, including github that don't render properly with 55 so for those I use the "Open with" extension to open 52. I expect over time that number will increase.

**VistaLover** · March 21, 2022

17 hours ago, soggi said:

I noticed the Way Back Machine doesn't work anymore with NM27, with NM28 it works.

In UXP-based latest St52 (2022-02-25) (32-bit), the left/right arrows on the top header, that are used to move between previous/later captures of the selected URI, are no longer functional :

Error Console Log:

Timestamp: 21/03/2022 02:29:58
Error: TypeError: t.getRootNode is not a function
Source File: https://web.archive.org/_static/js/bundle-playback.js?v=poeZ53Bz
Line: 2

Timestamp: 21/03/2022 02:30:02
Error: TypeError: e is null
Source File: https://web.archive.org/_static/js/bundle-playback.js?v=poeZ53Bz
Line: 2

... which suggests UXP-incompatible code (ShadowRoot, first implemented in Fx63) is used now... :angry:

**Mathwiz** · March 21, 2022

On 3/19/2022 at 9:39 PM, DanR20 said:

Does anyone know what sites this pref actually works on? It's a no go for github or gitlab.

It's worse than that. I just found that setting either pref on Serpent 55 breaks chase.com.

I'm guessing that chase.com checks whether these features are enabled and tries to use them if present, but runs fallback code if they're not. (Surprising when so many sites just expect them to be fully implemented.) If 55's Web Components implementation is incomplete and/or buggy, then enabling either pref actually makes things worse.

**soggi** · March 21, 2022

While using NM28 I ran again into the "missing search engine plugins" problem (the browser integrated search bar in the upper right), espacially Google is missing. So I decided to dig deeper and finally solve the problem. All the plugins on the Pale Moon site work, except Google (try out your self: http://web.archive.org/web/20170712213834/https://addons.palemoon.org/search-plugins/) On my search about this problem I found this post:

On 8/31/2021 at 2:04 AM, RainyShadow said:

F@#$ them - Use the source, Luke

Huge collection here

So I tried https://mycroftproject.com/search-engines.html but this didn't satisfy me, so I read about the OpenSearch standard and found out this is just a small XML file (with links, some stuff and a Base64 encoded icon in it) which has to be placed inside the folder "searchplugins" of a browser's profile. The mycroftproject XML was really, really outdated (but still functional). I recoded the icon to a proper 16*16 Base64 PNG and put the latest search URL into the XML - and yes it works fine, and has a much lower size!

Please let me know if someone is interested in a mirror of properly formated search plugins, then I will add them to the New Moon (etc.) mirror -> soggi.org - tools. Additionally mirroring of all your beloved add-ons is also possible, just leave me a note (within this thread). I'm already thinking about outsourcing the mirror into an extra article where I can add more content (tips, tweaks - all this stuff which keeps myself occupied while using New Moon).

---------------------------------------------

17 hours ago, InterLinked said:

Call me paranoid, but this is why I keep copies of installers for things, just so I can be sure about them

I only have XPI files for the few extensions in New Moon, Mail News, etc. that I'm actually using, but I guess it's good that "they're there", now...

No, I won't call you paranoid (BTW I love Black Sabbath's Paranoid) - that's just longsighted! Personally I backed up whole FTP servers in the past (and hopefully will do in the future). Backing up files is extremely important in the vintage/retro computer scene.

---------------------------------------------

10 hours ago, VistaLover said:
In UXP-based latest St52 (2022-02-25) (32-bit), the left/right arrows on the top header, that are used to move between previous/later captures of the selected URI, are no longer functional :

Error Console Log:
Timestamp: 21/03/2022 02:29:58
Error: TypeError: t.getRootNode is not a function
Source File: https://web.archive.org/_static/js/bundle-playback.js?v=poeZ53Bz
Line: 2

Timestamp: 21/03/2022 02:30:02
Error: TypeError: e is null
Source File: https://web.archive.org/_static/js/bundle-playback.js?v=poeZ53Bz
Line: 2
... which suggests UXP-incompatible code (ShadowRoot, first implemented in Fx63) is used now...

When visiting https://web.archive.org/web/*/www.cmd.com on NM27/28 it looks like on the screenshots below. I think I have to move on and make NM28 to my daily driver, the Way Back Machine is really important to my soggi.org work!

kind regards
soggi

Edited March 21, 2022 by soggi

**roytam1** · March 21, 2022

On 3/20/2022 at 3:21 PM, soggi said:

@roytam1 I noticed the Way Back Machine doesn't work anymore with NM27, with NM28 it works. They may have changed something with their JS again like months ago...

example link: https://web.archive.org/web/*/www.cmd.com

kind regards
soggi

it uses something that can't polyfilled:

20:11:30.976 SyntaxError: invalid regular expression flag u 1 https://web.archive.org/static/bower_components/wayback-search-js/dist/vendors~main.8e27e80156b09ad9fd4c.chunk.js:3:273362

20:11:31.056 ReferenceError: ReactDOM is not defined 1 www.cmd.com:1681:2

20:11:31.082 Unhandled promise rejection TypeError: i.getAttributeNames is not a function
Stack trace:
n@https://archive.org/includes/build/js/ia-topnav.min.js?v=2cfc3e21:7:2744
i/</globalThis.litHtmlPolyfillSupport/w._$AC@https://archive.org/includes/build/npm/lit/polyfill-support.js?v=2cfc3e21:13:1890
[3]/X</<.value@https://archive.org/includes/build/js/ia-topnav.min.js?v=2cfc3e21:7:6103
[3]/X</<.value@https://archive.org/includes/build/js/ia-topnav.min.js?v=2cfc3e21:7:5606
i/</globalThis.litHtmlPolyfillSupport/w._$AI@https://archive.org/includes/build/npm/lit/polyfill-support.js?v=2cfc3e21:13:1052
[3]/W@https://archive.org/includes/build/js/ia-topnav.min.js?v=2cfc3e21:7:1448
[3]/sn</<.value@https://archive.org/includes/build/js/ia-topnav.min.js?v=2cfc3e21:7:10923
[3]/k</<.value@https://archive.org/includes/build/js/ia-topnav.min.js?v=2cfc3e21:2:13513
[3]/k</<.value@https://archive.org/includes/build/js/ia-topnav.min.js?v=2cfc3e21:2:13122
n/<@https://archive.org/includes/build/js/ia-topnav.min.js?v=2cfc3e21:2:12841
l@https://web.archive.org/static/bower_components/wayback-search-js/dist/vendors~main.8e27e80156b09ad9fd4c.chunk.js:3:420112
s/i._invoke</<@https://web.archive.org/static/bower_components/wayback-search-js/dist/vendors~main.8e27e80156b09ad9fd4c.chunk.js:3:419902
k/</<@https://web.archive.org/static/bower_components/wayback-search-js/dist/vendors~main.8e27e80156b09ad9fd4c.chunk.js:3:420538
r@https://archive.org/includes/build/js/ia-topnav.min.js?v=2cfc3e21:2:1210
c@https://archive.org/includes/build/js/ia-topnav.min.js?v=2cfc3e21:2:1417
["5s+n"]/it@https://web.archive.org/static/bower_components/wayback-search-js/dist/vendors~main.8e27e80156b09ad9fd4c.chunk.js:3:41645
["5s+n"]/at/<@https://web.archive.org/static/bower_components/wayback-search-js/dist/vendors~main.8e27e80156b09ad9fd4c.chunk.js:3:41869
.tXUg/r@https://web.archive.org/static/bower_components/wayback-search-js/dist/vendors~main.8e27e80156b09ad9fd4c.chunk.js:3:514056
1 vendors~main.8e27e80156b09ad9fd4c.chunk.js:3:265220
.RN6c/t.exports() vendors~main.8e27e80156b09ad9fd4c.chunk.js:3
["5s+n"]/ut() vendors~main.8e27e80156b09ad9fd4c.chunk.js:3
["5s+n"]/ct/</e<() vendors~main.8e27e80156b09ad9fd4c.chunk.js:3
["5mdu"]/t.exports() vendors~main.8e27e80156b09ad9fd4c.chunk.js:3
["5s+n"]/ct/<() vendors~main.8e27e80156b09ad9fd4c.chunk.js:3
h/<() archive.min.js:101
h() archive.min.js:101
c() archive.min.js:101
Ic/h() webcomponents-bundle.js:138

**nicolaasjan** · March 21, 2022

4 hours ago, soggi said:

While using NM28 I ran again into the "missing search engine plugins" problem (the browser integrated search bar in the upper right), espacially Google is missing. So I decided to dig deeper and finally solve the problem. All the plugins on the Pale Moon site work, except Google (try out your self: http://web.archive.org/web/20170712213834/https://addons.palemoon.org/search-plugins/) On my search about this problem I found this post:

So I tried https://mycroftproject.com/search-engines.html but this didn't satisfy me, so I read about the OpenSearch standard and found out this is just a small XML file (with links, some stuff and a Base64 encoded icon in it) which has to be placed inside the folder "searchplugins" of a browser's profile. The mycroftproject XML was really, really outdated (but still functional). I recoded the icon to a proper 16*16 Base64 PNG and put the latest search URL into the XML - and yes it works fine, and has a much lower size!

Please let me know if someone is interested in a mirror of properly formated search plugins, then I will add them to the New Moon (etc.) mirror -> soggi.org - tools. Additionally mirroring of all your beloved add-ons is also possible, just leave me a note (within this thread). I'm already thinking about outsourcing the mirror into an extra article where I can add more content (tips, tweaks - all this stuff which keeps myself occupied while using New Moon).

---------------------------------------------

<---snip--->

You can easily add search engines with the addon "Add-to-Search-Bar".

Is available in the Classic Add-ons Archive (caa:addon/add-to-search-bar).

For New Moon you'll have to edit the install.rdf of course.

I think this gives you properly formatted xml files.

Edited March 21, 2022 by nicolaasjan

**Ben Markson** · March 21, 2022

4 hours ago, soggi said:

So I tried https://mycroftproject.com/search-engines.html but this didn't satisfy me, so I read about the OpenSearch standard and found out this is just a small XML file (with links, some stuff and a Base64 encoded icon in it) which has to be placed inside the folder "searchplugins" of a browser's profile. The mycroftproject XML was really, really outdated (but still functional). I recoded the icon to a proper 16*16 Base64 PNG and put the latest search URL into the XML - and yes it works fine, and has a much lower size!

And another add-on that allows you to edit mozlz4 files (like search.json.mozlz4) is this one...
https://addons.mozilla.org/en-GB/firefox/addon/mozlz4-edit/versions/

I have...
https://addons.mozilla.org/firefox/downloads/file/3304367/mozlz4_edit-4.1.2-an+fx.xpi
,,,installed under ff52.9

Ben.

Sign In

My Browser Builds (Part 3)

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Recently Browsing 0 members