Jump to content

My Browser Builds (Part 3)

roytam1
 Share

Recommended Posts

Rod Steel

Rod Steel

Posted
Posted (edited)
8 hours ago, VistaLover said:

a subforum for Mac users (now locked in oblivion):

8 hours ago, VistaLover said:

The last macPM release was v29.1.0; the Mac build maintainer (now banned in the PM forums) expressed his intentions to continue releasing Mac builds (by reverting code MCP remove - does it sound familiar?) and, as you'd expect, that caused both MAT+MC to burn fuses...

Wow, i never knew how destructive is Moonchild and Tobin, they really destroying everything around them. Fascinating self-destruction.:cool: Autism really sucks.:thumbdown

autism peak.gif

Edited by Rod Steel
3
Link to comment
Share on other sites

NotHereToPlayGames

NotHereToPlayGames

Posted
Posted (edited)
9 hours ago, VistaLover said:

I kindly ask those few "allergic" to off-topic content to move along and ignore this...

:roll1:I've always "laughed mockingly" at those "allergic types" with their high-and-mighty undertones whenever they chime in with their pretentious "you are off-topic, please return to the topic at hand".  These "allergic types" need to grow up!  Look at ANY forum and "analayze" their content.  Try to find ONE, just ONE, where 90+ percent of the posts are "on-topic" (excluding forums so niche that only 10 members are active versus a forum with 1000 active members).  It is HUMAN NATURE for conversations to diverge a tad, SO WHAT.  Forums have a tendency, due to HUMAN NATURE, to be oh, just guessing, to be roughly 40% "off-topic".  So yeah, "don't waive your bony finger", let the discussion RUN ITS COURSE, period.  It is HUMAN NATURE and makes for a more pleasant ambiance than having some "pretentious dude" waive a bony finger at each and every one of those 40% "off-topic" divergences, "you are off-topic, please return to the topic at hand".  I'd personally ban the "bony finger" dude over the topic-divergers, but maybe, just maybe, that might be because I just "diverged" herein.  :buehehe:

Edited by NotHereToPlayGames
1
Link to comment
Share on other sites
baluw

baluw

Posted
Posted
9 hours ago, roytam1 said:

it may because it tries to detect a custom URL scheme with javascript to see if there is a program can deal with spotify "URL" and give a spotify download if there is none, and the mechanism it use may be blocked by latest security patches.

I believe this also occured with other apps such as Winamp and Nero, which I am sure do not use any JS to check whether the app is already installed.

Link to comment
Share on other sites
RainyShadow

RainyShadow

Posted
Posted
5 hours ago, baluw said:

I believe this also occured with other apps such as Winamp and Nero, which I am sure do not use any JS to check whether the app is already installed.

Check in a new clean profile without any extensions. Maybe your adblocker or something else messes with the custom protocols used by these apps (or their detection). 

 

Link to comment
Share on other sites
VistaLover

VistaLover

Posted
Posted

Official Basilisk 52.9.2021.11.14 has been released, a day after a botched 52.9.2021.11.13 release... :whistle:; platform-wise, I expect it to be on par with Pale Moon 29.4.2.1, but is there something application-specific we could port over to Serpent 52.9.0?

http://archive.palemoon.org/source/basilisk-2021.11.13-source.tar.xz

https://fossies.org/diffs/basilisk/2021.09.27_vs_2021.11.13/

http://archive.palemoon.org/source/basilisk-2021.11.14-source.tar.xz

https://fossies.org/diffs/basilisk/2021.11.13_vs_2021.11.14/

@roytam1, what do you think? ;)

1
Link to comment
Share on other sites
roytam1

roytam1

Posted
  • Author
Posted
3 hours ago, VistaLover said:

Official Basilisk 52.9.2021.11.14 has been released, a day after a botched 52.9.2021.11.13 release... :whistle:; platform-wise, I expect it to be on par with Pale Moon 29.4.2.1, but is there something application-specific we could port over to Serpent 52.9.0?

http://archive.palemoon.org/source/basilisk-2021.11.13-source.tar.xz

https://fossies.org/diffs/basilisk/2021.09.27_vs_2021.11.13/

http://archive.palemoon.org/source/basilisk-2021.11.14-source.tar.xz

https://fossies.org/diffs/basilisk/2021.11.13_vs_2021.11.14/

@roytam1, what do you think? ;)

they pushed something they don't want to be published, like first post-git source release.

platform code of basilisk-2021.11.13-source.tar.xz is the same as pm29.4.2 while basilisk-2021.11.14-source.tar.xz's one uses same base as pm29.4.2.1.

 

basilisk-2021.11.13-source.tar.xz removed telemetry, safe browsing, tracking protection (do not track, and more), and some building system code changes. see https://github.com/roytam1/palemoon-source-tracking/commits/tracking for details.

while basilisk-2021.11.14-source.tar.xz only has some bugfix ported from pm29.4.2.1 and forced bundle emoji font and thats all, I can even just cherry-picking from tracking branch to complete this mini branch in https://github.com/roytam1/palemoon-source-tracking/commits/basilisk-20211114.

 

2
Link to comment
Share on other sites
VistaLover

VistaLover

Posted
Posted
29 minutes ago, roytam1 said:

while basilisk-2021.11.14-source.tar.xz only has some bugfix ported from pm29.4.2.1 and forced bundle emoji font and that's all

... All I can tell you is that 2021.11.13 was BAD,

https://forum.palemoon.org/viewtopic.php?f=61&t=27581

https://forum.palemoon.org/viewtopic.php?p=221571#p221571

thus, 2021.11.14 had to be rush-released... ;)

BTW, I never cease to admire you for your unwavering dedication to us all... :wub:

1
Link to comment
Share on other sites
roytam1

roytam1

Posted
  • Author
Posted
54 minutes ago, VistaLover said:

... All I can tell you is that 2021.11.13 was BAD,

https://forum.palemoon.org/viewtopic.php?f=61&t=27581

https://forum.palemoon.org/viewtopic.php?p=221571#p221571

thus, 2021.11.14 had to be rush-released... ;)

BTW, I never cease to admire you for your unwavering dedication to us all... :wub:

not surprised as 20211113 removed a big chunk of code, just a bit surprised that they didn't ever try to run compiled binaries before releasing.

2
Link to comment
Share on other sites
j7n

j7n

Posted
Posted
On 11/16/2021 at 12:34 PM, Rod Steel said:

That's a big mistake IMHO. Logically find everything for XP in XP subforum. I would not guess in year that for browsers for old OS was created new special subforum.

These browsers also run on my main OS Windows 2003, and I use them under Windows 7 too for convenience, familiar interface, included video decoder, removed anti-features, and various small fixes. Everytime I posted on the XP forum because that is where most people were, I expected to be kicked out for off-topic because I don't have WinXP anymore.

Recently YouTube changed something, which doesn't allow to go directly to Subscriptions from New Moon 28. A white page appears, and I must click the sidebar. Serpent still goes to Subscriptions, with a longer delay.

4
Link to comment
Share on other sites
roytam1

roytam1

Posted
  • Author
Posted
4 hours ago, VistaLover said:

... All I can tell you is that 2021.11.13 was BAD,

https://forum.palemoon.org/viewtopic.php?f=61&t=27581

https://forum.palemoon.org/viewtopic.php?p=221571#p221571

thus, 2021.11.14 had to be rush-released... ;)

BTW, I never cease to admire you for your unwavering dedication to us all... :wub:

got some time to build it, and the missing of Services.telemetry breaks everything: 

15:17:46.896 1637219866894	addons.xpi	ERROR	startup failed:
[Exception... "Component returned failure code: 0x80570018 (NS_ERROR_XPC_BAD_IID) [nsIJSCID.getService]"
  nsresult: "0x80570018 (NS_ERROR_XPC_BAD_IID)"
  location: "JS frame :: resource://gre/modules/XPCOMUtils.jsm :: XPCU_serviceLambda :: line 230"  data: no]
 Stack trace:
 XPCU_serviceLambda()@resource://gre/modules/XPCOMUtils.jsm:230
 < get()@resource://gre/modules/XPCOMUtils.jsm:198
 < checkForChanges()@resource://gre/modules/addons/XPIProvider.jsm:3713
 < startup()@resource://gre/modules/addons/XPIProvider.jsm:2773
 < callProvider()@resource://gre/modules/AddonManager.jsm:234
 < _startProvider()@resource://gre/modules/AddonManager.jsm:787
 < startup()@resource://gre/modules/AddonManager.jsm:968
 < startup()@resource://gre/modules/AddonManager.jsm:3025
 < observe()@resource://gre/components/addonManager.js:65 1 Log.jsm:753
	App_append resource://gre/modules/Log.jsm:753:9
	log resource://gre/modules/Log.jsm:389:7
	error resource://gre/modules/Log.jsm:397:5
	startup resource://gre/modules/addons/XPIProvider.jsm:2896:7
	callProvider resource://gre/modules/AddonManager.jsm:234:12
	_startProvider resource://gre/modules/AddonManager.jsm:787:5
	startup resource://gre/modules/AddonManager.jsm:968:9
	startup resource://gre/modules/AddonManager.jsm:3025:5
	observe resource://gre/components/addonManager.js:65:9

15:17:47.001 TypeError: Services.telemetry is undefined 1 resource://gre/components/SanityTest.js:69:7

15:17:47.602 TypeError: telemetry is undefined 1 resource://gre/components/nsBlocklistService.js:701:5

15:17:57.151 A promise chain failed to handle a rejection. Did you forget to '.catch', or did you forget to 'return'?
See https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise

Date: Thu Nov 18 2021 15:17:47 GMT+0800
Full Message: TypeError: Services.telemetry is undefined
Full Stack: _updateTelemetry@resource://gre/modules/osfile/osfile_async_front.jsm:459:9
post/<@resource://gre/modules/osfile/osfile_async_front.jsm:438:11
TaskImpl_run@resource://gre/modules/Task.jsm:318:42
process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:931:23
walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:812:7
scheduleWalkerLoop/<@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:746:11
 1 resource://gre/modules/osfile/osfile_async_front.jsm:459

15:19:24.963 TypeError: Services.telemetry is undefined 1 resource://gre/modules/PlacesDBUtils.jsm:56:9

15:20:04.063 TypeError: Services.telemetry is undefined 1 resource://global/content/viewSourceUtils.js:93:5

15:20:06.101 TypeError: Services.telemetry is undefined 1 resource://gre/modules/PageThumbs.jsm:223:7
	captureToCanvas/< resource://gre/modules/PageThumbs.jsm:223:7
	_captureToCanvas resource://gre/modules/PageThumbs.jsm:297:7
	captureToCanvas resource://gre/modules/PageThumbs.jsm:222:5
	capture/< chrome://browser/content/browser-ctrlTab.js:59:9
	shouldStoreThumbnail resource://gre/modules/PageThumbs.jsm:266:7
	capture chrome://browser/content/browser-ctrlTab.js:49:5
	handleEvent/< chrome://browser/content/browser-ctrlTab.js:86:15

 

3
Link to comment
Share on other sites
VistaLover

VistaLover

Posted
Posted (edited)
On 11/18/2021 at 5:37 AM, roytam1 said:

just a bit surprised that they didn't ever try to run compiled binaries before releasing.

... Nah, not surprised myself...<_< ; the Pale Moon unstable channel was terminated last September (in fairness, not many were using it ;) ) and official Basilisk is in a perpetual BETA status; so, the end recipient is expected to be the guinea pig... :angry:

Plus, I think MCP's judgement has been impacted lately, namely with their semi-psychotic perception of enemies everywhere, and dealing with this "threat" is what consumes most of their energy currently (e.g. alienating former co-devs, moving to private repos, DMCA-ing fork repos, etc.) ...

On 11/18/2021 at 5:37 AM, roytam1 said:

20211113 removed a big chunk of code

I recollect saying in these threads that MCP were "good" at removing existing (inherited) code - like WinXP/WinVista/Android/MacOS/EME/WebRTC/WebExtension/Container/Firefox legacy extension/FUEL/marqee support (and probably other things I forget about), but not that good at writing original new code to tackle the demands of the Chromium-dominated web... This latest blunder negates the first part of my assessment... But, I guess, I shouldn't be that harsh; everyones's entitled to a "bad day"/"happens in the best of families"/etc. :rolleyes:

Edited by VistaLover
2
Link to comment
Share on other sites
Tomcat76

Tomcat76

Posted
Posted

Just want to mention that the Add-ons Manager is still borked for me in Serpent52 build 20211113 (basilisk52-g4.8.win32-git-20211113) on XP 32-bit.  I have downloaded every version in between this build and the one I used before, and it looks like build 20210918 is the last one to work properly for me.
 
The issue with build 20210925 and newer is that all addons show as disabled (even when they are not) and that some aren't even shown.
 
After reverting to build 20210918, I also had to overwrite extensions.json with an older backup otherwise many addons would show up with a yellow exclamation mark above their title.  Right-clicking this exclamation mark and clicking "Show more information" gives a blank page.
 
Is there anything I can do to remedy this?  I'm currently back on build 20210918 because I need the ability to quickly toggle an addon on or off.
 
Attachments: Add-ons Manager in Serpent52 20211113 vs Serpent52 20210918.

serpent-addons.jpg

serpent-addons-20210918.jpg

Link to comment
Share on other sites
NotHereToPlayGames

NotHereToPlayGames

Posted
Posted
7 minutes ago, VistaLover said:

and official Basilisk is in a perpetual BETA status

Not to poke the bear, but how is that any different from any other browser discussed herein?  When did consumers become satisfied with labeling any "weekly" as 'stable' but reserve the 'beta' label for "nightly"?  Why should any of us have to update our browser "weekly"?  We don't gain anything by "weekly" updates outside of establishing some sort of "habit".  We are creatures of habit, but when did the consumer become satisfied with "It's Saturday, time to update my browser" ???

1
Link to comment
Share on other sites
VistaLover

VistaLover

Posted
Posted (edited)

@Tomcat76:

Have you tried to update CTR v1.6.9.1 to the Basilisk-specific version 1.7.8.2019.10.27 ?

https://github.com/Aris-t2/ClassicThemeRestorer/releases/tag/1.7.8.2019

I'm not seeing the AOM breakage you report (still on St52 2021-10-08 here); it probably has to do with an extension/setting of yours that affects the AOM; does it happen on a fresh St52 profile, after installing a test extension? if not, the culprit exists within your current, dirty, profile...

Sadly, I have to leave now for a few hours, thus not able to offer anything more substantial as help... :(

Edited by VistaLover
3
Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

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