Jump to content

My Browser Builds (Part 1)


Recommended Posts

Yes, I remember using IE 5.x and 6.x back in 2003-2006 (before I discovered Firefox) and it seemed to be the most well supported at the time.

Looking at now, I think Google has employed similar anti competitive tactics with regard to Chrome; it isn't necessarily a better browser, it's just that Google has deliberately done some shady things to make it look better than it really is (for example, deliberately using a deprecated JS API in YouTube which *no other browser supports*), and has leveraged this on their user base to unfairly increase Chrome's market share at its competitors' expense, primarily by making them look bad.

It reminds me an awful lot of how MS made Netscape look bad by deliberately configuring Windows (and manipulating various key standards) in such a way that Netscape would break in various subtle ways. The unsuspecting user, of course, didn't care and went to IE because it rendered pages better, ran faster, and didn't crash.

It's been my observation that history tends to repeat itself, and I find it particularly ridiculous that Google vs. Firefox is playing out almost *exactly* 20 years after MS vs. Netscape, and in virtually the same manner to boot!

c

Edited by cc333
Link to comment
Share on other sites


https://www.earthcam.com/

Earthcam webcams show up as a black screen on my new install & profile of NM 28.6.0a1 (2019-05-03)

 

https://www.earthcam.com/site/player_help.php

The Earthcam test reads Mozilla 60.9 / flash 32 / and javascript working. 

 

https://www.earthcam.net/support/systemcheck.php

This test created a pop-up saying,  "The page isn’t redirecting properly.  Pale Moon has detected that the server is redirecting the request for this address in a way that will never complete.  This problem can sometimes be caused by disabling or refusing to accept cookies."

I disabled all privacy & ublock, but it still wont work.

 

hmmm :dubbio:  but Earthcam works okay in moebius (2019-04-05)

The test of moebius reads Mozilla 55 / flash 32 / and javascript working

 

oh dear!  any ideas?

 


 

 

 

 

Edited by taos
Link to comment
Share on other sites

1 hour ago, taos said:

https://www.earthcam.com/

Earthcam webcams show up as a black screen on my new install & profile of NM 28.6.0a1 (2019-05-03)

 

https://www.earthcam.com/site/player_help.php

The Earthcam test reads Mozilla 60.9 / flash 32 / and javascript working. 

 

hmmm :dubbio:  but Earthcam works okay in moebius (2019-04-05)

The test of moebius reads Mozilla 55 / flash 32 / and javascript working

 

oh dear!  any ideas?

First try a SSUAO to spoof FF 52: something like

general.useragent.override.earthcam.com;Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.9) Gecko/20100101 Firefox/52.9

It could be the same problem as Instagram. NM 28 and Serpent 52 spoof FF 60.9, but don't support some of FF 60.9's Javascript, so a few sites see the "60.9," feed NM/Serpent incompatible Javascript, and break. Moebius works because it spoofs FF 55, which predates Quantum.

If that doesn't work, try the previous version of NM 28; it's not uncommon for one of the weekly updates to break some sites. If that's the problem, it'll probably be fixed by next week.

Link to comment
Share on other sites

@Mathwiz 

Yes, an SSUAO was all that was needed.

In about:config there was about 40 existing overrides with a variety of spoofs.

I copied and pasted an existing 52.9 spoof into a new string. 

It was very easy, due to the great advice given here.

Thanks again :thumbup

Link to comment
Share on other sites

On 4/27/2019 at 11:16 AM, roytam1 said:

New build of Serpent/UXP for XP!

Test binary:
Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20190427-3424afcca-xpmod.7z

In UXP commit 33ebc88 , platform (i.e. Goanna) version was bumped to 4.2.0, so I think the Serpent52 repo packages starting with the quoted above (and including the latest one) should be renamed to properly reflect that change:

basilisk52-g4.1.win32-git-20190427-3424afcca-xpmod.7z => basilisk52-g4.2.win32-git-20190427-3424afcca-xpmod.7z

basilisk52-g4.1.win32-git-20190504-d9d9d1ed8-xpmod.7z => basilisk52-g4.2.win32-git-20190504-d9d9d1ed8-xpmod.7z

(for brevity, only win32 packages mentioned here...)

On 4/27/2019 at 11:16 AM, roytam1 said:

* since MCP deleted lots of files, this might affect Serpent's functionality of updating WE extension. please test and report if there is any irregularities.

In its current incarnation, Serpent 52.9.0 is incapable of contacting AMO to check for installed WE updates; there are two about:config prefs that control extension updates, the first is the main one and the other is a fallback one,

extensions.update.url
extensions.update.background.url

Due to MCP changes, currently both point to the Basilisk extension repository (ABO) :

https://addons.basilisk-browser.org/?component=aus&reqVersion=%REQ_VERSION%&id=%ITEM_ID%&version=%ITEM_VERSION%&maxAppVersion=%ITEM_MAXAPPVERSION%&status=%ITEM_STATUS%&appID=%APP_ID%&appVersion=%APP_VERSION%&appOS=%APP_OS%&appABI=%APP_ABI%&locale=%APP_LOCALE%&currentAppVersion=%CURRENT_APP_VERSION%&updateType=%UPDATE_TYPE%&compatMode=%COMPATIBILITY_MODE%

ABO does not contain any WE addons; to mitigate that, if WE addons (from AMO originally) are installed in Serpent 52.9.0, you should change the value of at least one of those prefs to point to AMO; e.g. in my installation I modified extensions.update.background.url to have a value of 

https://versioncheck.addons.mozilla.org/update/VersionCheck.php?reqVersion=%REQ_VERSION%&id=%ITEM_ID%&version=%ITEM_VERSION%&maxAppVersion=%ITEM_MAXAPPVERSION%&status=%ITEM_STATUS%&appID=%APP_ID%&appVersion=52.9&appOS=%APP_OS%&appABI=%APP_ABI%&locale=%APP_LOCALE%&currentAppVersion=%CURRENT_APP_VERSION%&updateType=%UPDATE_TYPE%&compatMode=%COMPATIBILITY_MODE%

But in reality, the kind of WebExtensions compatible with Serpent 52 are, more often than not, previous/older versions that are not being updated and if they are, they (of course) target Quantum (Fx >=57.0) with its richer set of WE APIs (compared to the ones present in Serpent); so by contacting AMO you risk

1. Having a legacy extension installed in Serpent 52 get updated to a non-compatible WE version of it... (remember, even though Serpent may advertise itself to AMO as Firefox 52.x, it has only a subset of the WE APIs found in Fx 52 :().

2. Having a WE addon get updated to a non-compatible (WE) version of it.

An example from my own usage is

https://addons.mozilla.org/el/firefox/addon/tab-tally/versions/

The one version fully compatible with St52 is XUL v0.1.1 (you can find it in CAA); if you check for updates on AMO, you'll be updated to v1.4.0, of the WE flavour, that does not work as expected in St52! :angry:

That is why I have configured Serpent to NOT auto-update installed extensions...

 

Link to comment
Share on other sites

I used to go to http://download.microsoft.com/ to search and download MS stuff. Now using Serpent I found something is unusual about searching, as below:1.thumb.PNG.5eda279ca6762bd4b236a30ca9833448.PNG

Click the magnifying glass will not show a search bar; the radio button seems to be pressed down when clicking the blank; I can input words which is not shown, but search suggestions will show up.

In Firefox 52, the same page will jump to a searching page when click the magnifying glass:

2.thumb.PNG.49490362bda8838c31a76b1780c5c84c.PNG

I doubt either behavior should not be right (though I prefer the old Firefox52 way); Please confirm and see if something could be fixed.

Link to comment
Share on other sites

1 hour ago, Destro said:

If you press the cart then press the magnifying glass it works as it should.  Or just click the link https://www.microsoft.com/en-us/search?q=

Pressing cart will get to https://www.microsoft.com/en-us/store/cart first, then pressing (the new) magnifying glass will work. And the link https://www.microsoft.com/en-us/search?q= is more direct. Yet still, Serpent is having problem to render the original page, and I want to give feedback.

14 minutes ago, kitaro1 said:

Serpent 55 http://prnt.sc/nldpwy

Palemoon28.4.0 http://prnt.sc/nldq6n

The search and search icon is normal. :)

 

I should clarify that I am on Serpent 52 (20190503).

Link to comment
Share on other sites

10 hours ago, luweitest said:

Now using Serpent I found something is unusual about searching, as below:

10 hours ago, luweitest said:

Click the magnifying glass will not show a search bar; the radio button seems to be pressed down when clicking the blank; I can input words which is not shown, but search suggestions will show up.

... On Serpent 52.9.0, it appears to be Javascript related (as Web Console and/or Browser Console would reveal):

WEe7OYp.jpg

Clicking the Learn More link takes you to a MDN article: 

https://developer.mozilla.org/el/docs/Web/JavaScript/Reference/Errors/Not_a_function

Possibly unsurprisingly (now that MS and Google have turned into best pals), clicking the magnifying glass works as expected in Google Chrome (51.0.2679.0 in my case):

i2QwxNP.jpg

@roytam1: If it is reproducible in latest official Basilisk (52.0.2019.03.27), perhaps the bug should be reported to the official Pale Moon forum (but NOT by a Serpent 52 user), so that MCP are made aware and, hopefully, come up with a fix... ;)

Link to comment
Share on other sites

On 4/27/2019 at 3:30 AM, roytam1 said:


I'm getting this crash when launching the 64-bit version in XP x64.  Any advice please?

palemoon3.png.60c7a1874b4365a81c13958671c2caca.png

I tried it with a new, clean profile as well.

Thank you.

Link to comment
Share on other sites

16 hours ago, VistaLover said:

An example from my own usage is

https://addons.mozilla.org/el/firefox/addon/tab-tally/versions/

The one version fully compatible with St52 is XUL v0.1.1 (you can find it in CAA); if you check for updates on AMO, you'll be updated to v1.4.0, of the WE flavour, that does not work as expected in St52! :angry:

I'm not sure that's right. I just loaded Tab Tally v.1.4.0 in FF 52, St 52, and St 55, and AFAICS it works identically in all three versions.

I don't think it works correctly; the total number of tabs doesn't update when you close a tab until you click it. But at least it messes up the same way in FF 52 as in Serpent. I suspect it's just buggy in older FF versions, and that affects Serpent as well as "genuine" FF.

Also, according to the page above, the change in v1.4.0 was to expand compatibility down to FF 42 and above. (V1.3.0 worked in FF 48 and above.) I find it hard to believe Serpent 52 lacks WE APIs that were present in FF 42!

Link to comment
Share on other sites

3 hours ago, mockingbird said:


I'm getting this crash when launching the 64-bit version in XP x64.  Any advice please?

palemoon3.png.60c7a1874b4365a81c13958671c2caca.png

I tried it with a new, clean profile as well.

Thank you.

Same just tested it on 2003 64bit, I do not get an error, it just immediately closes.  Also tried with clean profiles.

New moon 28 64bit works fine tho

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...