Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


roytam1

My build of New Moon (temp. name) a.k.a. Pale Moon fork targetting XP

Recommended Posts

New build of Serpent/UXP for XP!

Test binary:
Win32 https://o.rths.cf/basilisk/basilisk52-g4.4.win32-git-20190803-3170ee769-xpmod.7z
Win64 https://o.rths.cf/basilisk/basilisk52-g4.4.win64-git-20190803-3170ee769-xpmod.7z

source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom

NM28XP build:
Win32 https://o.rths.cf/palemoon/palemoon-28.7.0a1.win32-git-20190803-3170ee769-xpmod.7z
Win64 https://o.rths.cf/palemoon/palemoon-28.7.0a1.win64-git-20190803-3170ee769-xpmod.7z

Official repo changes since my last build:
- Issue #1156 - Location Bar Preferences Checkboxes (93ceb8281)
- Merge pull request #1200 from flewkey/master (a4584c732)
- Update SQLite to 3.29.0 (154532072)
- Hide and disable open_all/cut/copy/delete/properties when opening bookmarks/history context menu with no selection (3170ee769)

  • Like 5

Share this post


Link to post
Share on other sites

New build of BOC/UXP for XP!

Test binary:
MailNews Win32 https://o.rths.cf/boc-uxp/mailnews.win32-20190803-211bb28-uxp-3170ee769-xpmod.7z
Browser-only Suite Win32 https://o.rths.cf/boc-uxp/bnavigator.win32-20190803-211bb28-uxp-3170ee769-xpmod.7z

source patch (excluding UXP): https://o.rths.cf/boc-uxp/boc-uxp-src-xpmod-20190720.7z

No Official repo changes since my last build.

For UXP changes please see above.

  • Like 2

Share this post


Link to post
Share on other sites

New New Moon 27 Build!

32bit https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190803-23551d191-xpmod.7z
32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190803-23551d191-xpmod-sse.7z
32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190803-23551d191-xpmod-ia32.7z

64bit https://o.rths.cf/palemoon/palemoon-27.9.6.win64-git-20190803-23551d191-xpmod.7z

source repo: https://github.com/roytam1/palemoon27

repo changes since my last build:
- import change from rmottola/Arctic-Fox:
 - Bug 1128001 - Workaround ANGLE DEPTH16 being DEPTH24_STENCIL8. (144bc3839)
 - Bug 1038839 - Use type information for alias analysis. r=jandem (7f562bcc2)
 - Bug 1141797. r=smaug. (6ac0692bd)
 - Bug 1143470 - Add BUG_COMPONENT to moz.build files in toolkit and xulrunner. r=gavin (3fee7e2d5)
 - Bug 1083344 - Add "allow" sandbox rules to fix mochitests on OSX 10.9 and 10.10. r=smichaud (40c3323a5)
 - Bug 1083344 - Tighten rules for Mac OS content process sandbox on 10.9 and 10.10. r=smichaud (a1102b817)
 - Bug 1151974 P1 Delay Cache Context start until previous Context has completed. r=ehsan (20598fa6a)
 - Bug 1130686 - Add test for service worker client.focus. (e4d836af7)
 - Bug 1151916 - Set worker principalinfo on cache load. r=bkelly (4d55b31fe)
 - Bug 1139513 - Warn and gather data if ServiceWorker hits max workers per domain limit. r=bent, r=rvitillo (44c59a9cb)
 - Bug 1148354 - Deprecate the doppler effect from the PannerNode. r=ehsan (6de4e13ca)
 - Bug 1148942 - Ensure that the registration of empty service workers succeeds; r=bent (edbb09fdf)
 - Bug 1148496 - Allow to set an interface member as [Deprecated] in WebIDL. r=bz,smaug (43f554139) (23551d191)

  • Like 3

Share this post


Link to post
Share on other sites

New regular/weekly KM-Goanna release:
https://o.rths.cf/kmeleon/KM76.2-Goanna-20190803.7z

Changelog:

Out-of-tree changes:
* update Goanna3 to git e48fcd77f..23551d191:
- import change from rmottola/Arctic-Fox:
 - Bug 1128001 - Workaround ANGLE DEPTH16 being DEPTH24_STENCIL8. (144bc3839)
 - Bug 1038839 - Use type information for alias analysis. r=jandem (7f562bcc2)
 - Bug 1141797. r=smaug. (6ac0692bd)
 - Bug 1143470 - Add BUG_COMPONENT to moz.build files in toolkit and xulrunner. r=gavin (3fee7e2d5)
 - Bug 1083344 - Add "allow" sandbox rules to fix mochitests on OSX 10.9 and 10.10. r=smichaud (40c3323a5)
 - Bug 1083344 - Tighten rules for Mac OS content process sandbox on 10.9 and 10.10. r=smichaud (a1102b817)
 - Bug 1151974 P1 Delay Cache Context start until previous Context has completed. r=ehsan (20598fa6a)
 - Bug 1130686 - Add test for service worker client.focus. (e4d836af7)
 - Bug 1151916 - Set worker principalinfo on cache load. r=bkelly (4d55b31fe)
 - Bug 1139513 - Warn and gather data if ServiceWorker hits max workers per domain limit. r=bent, r=rvitillo (44c59a9cb)
 - Bug 1148354 - Deprecate the doppler effect from the PannerNode. r=ehsan (6de4e13ca)
 - Bug 1148942 - Ensure that the registration of empty service workers succeeds; r=bent (edbb09fdf)
 - Bug 1148496 - Allow to set an interface member as [Deprecated] in WebIDL. r=bz,smaug (43f554139) (23551d191)

* Notice: the changelog above may not always applicable to XULRunner code which K-Meleon uses.

A goanna3 source tree that has kmeleon adaption patch applied is available here: https://github.com/roytam1/palemoon27/tree/kmeleon76

  • Like 3

Share this post


Link to post
Share on other sites

@mraeryceos

... My previous assessment was based on your initial report, stating that:

On 8/1/2019 at 5:06 AM, mraeryceos said:

I tried several things, which eventually led me to rebuild my browser from scratch.

and I took (perhaps mistakenly?) "rebuild my browser from scratch" to mean build a new New Moon 28 profile from scratch; but you're now possibly contradicting yourself, as in:

28 minutes ago, mraeryceos said:

I ended up continuing to use the browser profile without rebuilding it from scratch :-)

So, which was it? In any case, I'm more than happy you ended up with a smooth-running browser! :cheerleader:

Share this post


Link to post
Share on other sites
Posted (edited)
19 hours ago, roytam1 said:

official build got errors as well

Many thanks for checking this out :wub:

19 hours ago, roytam1 said:

but it is not good to post bug report to their side with my account.

With all due respect, how is this going to contribute to current/future bug resolution on the UXP platform, that we also share here? 

1. Moonchild won't accept bug reports if they came from unbranded forks (NM28+St52) users (if you ask me, he himself should test if present in his official builds, before dismissing those users, but all parties here realize this is never gonna happen!)

2. Effort has been taken recently in these forks (with initial requests by @TechnoRelic and other members, put in place by PRs kindly authored by @Mathwiz) to direct all issue reports here and, ultimately, to have them reviewed by the forks' maintainer, i.e. you :)

3. I'd argue that the majority of the fork(s) users do so because, either by choice or necessity, find themselves using an OS not sanctioned by the upstream devs (namely XP and Vista), and who (which is currently the case with me) don't have immediate/easy access to the officially sanctioned/supported OSes (Win7+).

4. Moonchild, in general, dislikes people posting issues directly in his GitHub issue tracker (apparently only reserved to a team of selected developers/"sidekicks"), instead prefers his users to post first to the official forum, and then he could "triage" them there as he sees fit <_<.

My humble opinion is that you should post the issue in the forums, with concrete proof it was diagnosed in an official build (so, no references or links to here); that way, Moonchild will have no justification to dismiss the bug report, even if it came from his worst enemy on this planet (which, obviously, you're not! :)).

I see only two other approaches:

1. Somehow push code yourself to your custom UXP branch to rectify reported issue(s) on your own.

2. This broader community is otherwise in need of a person/member that:

a. Has a (whitelisted) official forum (forum.palemoon.org) account
b. Optionally, has also a GitHub account
c. Is a user of a UXP forked application, namely New Moon 28 and Serpent 52.9.0
d. Has easy access to an OS that supports the official counterpart applications, i.e. Pale Moon 28 and Basilisk 52.9.20xx.xx.xx)
e. Is able to reproduce/confirm bugs (found initially in the forks) in the official builds. 
f. Is able to post a no-frills coherent report in the forums, and then let MCP et co. do the rest

FWIW, last time I asked a favour from such a person, he kindly declined (and I have no right whatsoever to blame him...).

Again, this is NOT about my petty bug (for which I've already found and posted a working fix); it's about the course of actions one is supposed to follow with regards to meaningful UXP bug report and hopeful resolution!

Thanks again for your time reading this, thanks eternally for your efforts and binaries :wub:

(... back now to deploying a strategy on how to combat a 42 Celsius heatwave pestering us for the next two days :()

Edited by VistaLover
English
  • Like 1

Share this post


Link to post
Share on other sites

@VistaLover

I started rebuilding the browser from scratch (yes the profile, but also another folder with another instance of the program files).  I started to, is the key phrase here.  I didn't continue, because I noticed that I was no longer having issues with CPU racing.  The only thing I changed was the --no-remote switch.  So now I am back to using the old profile, and the old program files that have been updated-in-place several times over the years.

Sorry, I thought it was clear.

  • Like 1

Share this post


Link to post
Share on other sites

(PM28, WinXP)

mraeryceos said:


I started rebuilding the browser from scratch (yes the profile, but also another folder with another instance of the program files). I started to, is the key phrase here. I didn't continue, because I noticed that I was no longer having issues with CPU racing. The only thing I changed was the --no-remote switch. So now I am back to using the old profile, and the old program files that have been updated-in-place several times over the years.


Very interesting. Were the culprits some specific websites, or just in the sense of "too many tabs open"?
Makes me wonder why this happens. Anyone have a guess?

Share this post


Link to post
Share on other sites
On 8/1/2019 at 5:00 PM, Mathwiz said:

Without uBlock Origin Updater, Serpent 55 (Moebius) will self-update to 1.18.4 (or possibly later)

 

On 8/1/2019 at 7:28 PM, VistaLover said:

Not according to tests I conducted prior to my reply above...

Steps to reproduce... (removed for brevity; see above)

Well, you're right - but so was I.

There are two update mechanisms in FF and its offshoots: manual and automatic. And believe it or not (I certainly didn't believe it until I confirmed it myself) on Serpent 55, they yield different results!

As you found, the manual process (where you ask the browser to check for updates) stops at 1.17.4. But the automatic process will eventually offer 1.21.2 (which is broken on St 55, as you noted). What the heck is going on here anyway?

I think I found the answer in these two prefs:

extensions.update.background.url;https://versioncheck-bg.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=%APP_VERSION%&appOS=%APP_OS%&appABI=%APP_ABI%&locale=%APP_LOCALE%&currentAppVersion=%CURRENT_APP_VERSION%&updateType=%UPDATE_TYPE%&compatMode=%COMPATIBILITY_MODE%

extensions.update.url;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=53.0&appOS=%APP_OS%&appABI=%APP_ABI%&locale=%APP_LOCALE%&currentAppVersion=%CURRENT_APP_VERSION%&updateType=%UPDATE_TYPE%&compatMode=%COMPATIBILITY_MODE%

You'll have to scroll to the right to see the relevant difference (it's subtle). The "appVersion=" query string passed to the server is the variable %APP_VERSION% in the extensions.update.background.url pref, but it's hard-coded as 53.0 in the extensions.update.url pref!

As it happens, uBO version 1.17.4 is the latest version claiming to run on FF versions 52.0 through 54.0. All later versions claim 55.0 or later is required. So when you manually check for updates, AMO only offers uBO version 1.17.4. but when the browser does it automatically, %APP_VERSION% gets replaced with 55.0, so AMO offers the latest version (1.21.2).

This discrepancy goes back at least as far as the 3/10/2018 version of Serpent 55. I'm surprised no one has stumbled across it before now. I'm guessing the hard-coded 53.0 was meant to fix incompatible updates being offered (Serpent 55 was forked from FF 53, with only a few changes back-ported from FF 54 and FF 55, so many add-ons targeted at FF 54 or 55 won't run, now including uBO 1.21.2), but whoever put it in (MCP?) forgot to make the same fix to the background pref. It would make more sense to hard-code 53.0 in both update prefs and eliminate this oddity.

Side note: if you go to about:addons, click Get Add-Ons, then click Find More Add-Ons, what AMO offers depends on your user agent. By default, it won't offer anything except a download of Firefox (even in FF compatibility mode), but if you use, say, a SSUAO to provide a "pure" FF user agent, it will offer either 1.17.4 or 1.21.2, depending on which FF version you pretend to be.

If you want to "live on the edge," you could put 55.0 in a SSUAO for AMO. If you also fix the background update pref, you wouldn't be offered any uBO updates past 1.17.4, but could still manually browse AMO and try later versions to see if they work (as mentioned, 1.18.4 will and 1.21.2 won't, but I haven't tried versions in between to find out where the "cutoff" is).

  • Like 2

Share this post


Link to post
Share on other sites
5 hours ago, VistaLover said:

how is this going to contribute to current/future bug resolution on the UXP platform, that we also share here? 

Mark's side should be fine for my bug report, just Matt's reaction is problematic. To prevent over-reaction from Matt, I'd prefer not posting bug reports.

But I think people may register in PM forum with different username and post bug report there.

Share this post


Link to post
Share on other sites
On 7/18/2019 at 7:32 PM, siria said:

Please elaborate, to figure out solutions?
The prob is, K-Meleon may be missing some essential things, but it also has lots of hidden features which simply aren't visible to unexperienced users.
For example most buttons have a handy right-click menu, which most people never discover just because they have no little-arrow as indication (example Home or Go-buttons)
A killer feature is the hidden privbar (View > Toolbars) with buttons for 1-click toggle of javascript, cookies etc.
Or the "about:about" page has lots of working links to more settings, incl. about:addons, which are not found anywhere in the menus, just because the GUI hasn't been updated in the last ten years or so, only the engine (install macro aboutabout to get at least a makeshift-menu)
Copy+search: select a text in a webpage and hit the search button (or similarly: select a text LINK and hit the Go-button)
Duplicate a tab: pull the tab into an empty space on tab bar (if any left ;-), or right-click on Go-button
If you want a closing cross on tabs: guess for this there's actually a GUI somewhere, perhaps in F2... (would have to look it up, am myself stuck on old version)
There are also macros for easy useragent-toggling, I recommend my "useragents2018" which also helps for easier managing site-UAs.

Thanks for the tips, the F2 open a world of personalization included close-tab-cross on tab. Indeed it's a browser more advanced then others about "mouse gesture". For example you can close a tab just double clicking on the tab itself.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...