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 for XP

Recommended Posts


Anyone else have an issue, when NM starts and about:home is set as home page, the search bar that is present there, for a second after starting the browser, looks like this?:

searchbar.thumb.png.e8da9055f7e3a56caf9ef6323cfb8fd7.png

All I know is that it came with last week's NM release. And also I know it's a very minor issue since it doesn't really affect my browsing experience, but I just want to know if it's something on my end that's suddenly causing this, or if it's something with the browser itself.

Share this post


Link to post
Share on other sites
57 minutes ago, Tamris said:

when NM starts and about:home is set as home page, the search bar that is present there, for a second after starting the browser, looks like this?:

... I can reproduce; I had to temporarily switch to the default theme (am using Dark Moon 2.3.0 otherwise) to notice it more clearly: for a fraction of a second, the embedded search bar (in the middle of about:home) appears truncated (i.e. shorter) when about:home is loaded for the first time, but then auto-resumes its normal length... NB that when DDG is set as the default search engine (which is the default setting), the search bar is shorter, because it is prepended by the DDG icon (at least in the default theme); when other search engines are user-selected, these come with no icon and an elongated search bar... 

1 hour ago, Tamris said:

All I know is that it came with last week's NM release

The changelog between buildID=20181221223321 and buildID=20181228225818 (for 32-bit) is:

https://github.com/MoonchildProductions/UXP/compare/ba81aaf...83cd966

The one relevant commit that easily stands out appears to be:

[PALEMOON] Initialize the search service asynchronously from 'about:home' and 'about:newtab' :

https://github.com/MoonchildProductions/UXP/commit/cb2f0f614362d3e986d585d6d1b4a2eaa20a1365

Hope your query is answered ;)

  • Like 2

Share this post


Link to post
Share on other sites
14 hours ago, Tamris said:

Anyone else have an issue, when NM starts and about:home is set as home page, the search bar that is present there, for a second after starting the browser, looks like this?: 

No problem. The home page is fast.

http://prntscr.com/m3mjfe

Share this post


Link to post
Share on other sites
Posted (edited)
On 12/31/2018 at 9:15 AM, Mathwiz said:

Well, I just tried [multiprocess mode] in Basilisk 52. The about:config Boolean preference above doesn't exist by default in either the XP or official build; I had to add it .

I didn't expect it to work, but it did! Task manager shows two Basilisk processes, just like the "old days." Guess all my add-ons are multiprocess-compatible.

Well, spoke too soon. One of my add-ons has turned out to be incompatible with multiprocess mode: the Classic Add-Ons Archive mentioned by @VistaLover not long ago. Have to disable multiprocess mode and restart in order to use that add-on. :(

Edit: And, just like that, I found another: Markdown Viewer, an add-on for reading .md files, doesn't work in multiprocess mode either; files just open as a blank tab. :angry:

This one was more annoying since I was trying to set up Basilisk as the default program to open .md files. Ended up having to create a separate profile, which I named "Single-process mode", disable multiprocess mode in that profile, and edit the "open" command in the registry thus:

"C:\Program Files (x86)\Basilisk\basilisk.exe" -no-remote -P "Single-process mode" -url "%1"

(Took quite a bit of trial-and-error to figure that one out, too.)

Edited by Mathwiz

Share this post


Link to post
Share on other sites
Posted (edited)
On 1/5/2019 at 4:07 AM, roytam1 said:

New build of basilisk/UXP for XP!

Test binary:
Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20190105-7fcb7f544-xpmod.7z
Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20190105-7fcb7f544-xpmod.7z

diff: https://o.rths.cf/basilisk/UXP-xp-gitdiff-20181110.7z

PM28XP build:
Win32 https://o.rths.cf/palemoon/palemoon-28.3.0a1.win32-git-20190105-7fcb7f544-xpmod.7z
Win64 https://o.rths.cf/palemoon/palemoon-28.3.0a1.win64-git-20190105-7fcb7f544-xpmod.7z

Official repo changes since my last build:
- [PALEMOON] Bug 1115369 - Use notifications instead of getViewItem for DownloadsView (a970e88a1)
- [PALEMOON] Bug 1115971 - Don't fall back to the Places title for downloads without the target file name annotation (1b414c2b9)
- [PALEMOON] Bug 1115972 - Don't fall back to the Places icon for downloads without the target file name annotation (8bd13f3a2)
- [PALEMOON] Bug 1120429 - Remove unused code handling nodeAnnotationChanged (1eab01b24)
- [PALEMOON] Bug 1115421 - Simplify download annotations handling in the Library (81265fae3)
- [PALEMOON] Bug 1115983 - Keep only minimal state information in the DataItem (e666c9a8e)
- [PALEMOON] Bug 1116176 - Create DownloadsHistoryDataItem and HistoryDownload objects (ac3159f02)
- [PALEMOON] Bug 1115379 - Streamline DownloadsViewItemController construction and remove now unneeded identifiers (927853bde)
- [PALEMOON] Bug 1117139 - Move code controlling the "download.xml" binding to a common place (f2f700514)
- [PALEMOON] Bug 1117139 - Move code controlling the "download.xml" binding to a common place (downloadsViewCommon.js) (df852eca4)
- [PALEMOON] Bug 1117141 - Part 1 of 2 - Bypass all the DownloadsDataItem properties (462332eee)
- [PALEMOON] Bug 1117141 - Part 2 of 2 - Refactor notifications and remove the DownloadsDataItem object (d6c976bf6)
- Fix typos (761b6eb25)
- [PALEMOON] Bug 1127867 - Use the new back-end property to get the size of downloads asynchronously (beeede618)
- [PALEMOON] Bug 1195279 - Fix typo in allDownloadsViewOverlay.js following landing of bug 1127867 (8cc3f3616)
- [PALEMOON] Bug 1129896 - Part 1 of 2 - Keep cached metadata for history downloads indefinitely (0b15a2b89)
- [PALEMOON] Bug 1129896 - Part 2 of 2 - Convert the shared front-end code to a JavaScript code module (551c6ff04)
- [PALEMOON] Bug 1135348 - Fix about:downloads by adding missing XPCOMUtils imports (909c3ee13)
- [PALEMOON] Initialize the search service asynchronously when calling 'BrowserSearch.addEngine()' (accd61429)
- [FFmpeg] Use new decode API with recent FFmpeg version. (515e0794f)
- [FFmpeg] Don't define AV_CODEC_ID_VPx with libavcodec 58 (68acfbb14)
- Merge pull request #921 from trav90/media-work (5920c1dc6)
- Avoid redefined macro warning in MediaFormatReader (7a39cd52e)
- Merge pull request #922 from trav90/media-work (626d40774)
- Merge pull request #920 from JustOff/PR_nsIBrowserSearchService_async_init_2 (bcf3df362)
- Merge pull request #917 from janekptacijarabaci/_testBranch_pm_downloads_rewrite (78ad9498a)
- Dont rely on 'this' staying alive long enough for getting favicons. (8a10092b5)
- Add Comodo IS < 6.3 64-bit to the dll blocklist (517f50298)
- Update UXP Coding Style guideline document (WIP) (eec3d00bb)
- Update UXP Coding Style guideline document (WIP) (7a22921c2)
- Update UXP Coding Style guideline document (WIP) (da0d462d6)
- Use getElementBoundingRect and element.ownerGlobal in FormSubmitObserver (f543892e4)
- Update HSTS preload list (483267ba9)
- Make MAX_CSS_VAR_LENGTH unsigned to avoid warnings. (dfce7fa7b)
- Remove proprietary constructor on AudioContext. (7fcb7f544)

My changes since my last build:
- update libaom to git rev c07e9d6ccf340843e8899e7da6b15a0893007bd5

Thanks Roytam1 for impressive work (at higher frequency update than FF/Chrome development:buehehe:)

Can someone confirm the importing of extensions+favorites we have to copy inside the new release this previous 2 folders:

basilisk(old)\

1) defaults\pref

2) browser\extensions

?

Edited by Vistaboy

Share this post


Link to post
Share on other sites

In my case at least, extensions & favorites are stored in my profile folder.

To find out where that is, open your old browser and type about:profiles. It will list all your profiles (most folks only have one) along with the paths to each.

You can do the same thing in your new browser too. Once you know where both profiles are, you can copy everything from your old browser's profile folder to your new one. (Close both browsers first.)

Even after copying everything to your new browser, you may still need to reinstall some add-ons. See post 1 in this thread for instructions on doing that.

And of course, if you're changing browser platforms (e.g., from Firefox to NM), some add-ons may not be compatible with your new browser and you'll have to look for alternatives.

Note: you don't need to go through all this when updating a browser to a newer version. Just back up the programs folder (e.g., C:\Program Files\basilisk or wherever you put yours) in case you need to revert, then copy everything from the update into the programs folder. No need to touch profiles in this case.

  • Like 2

Share this post


Link to post
Share on other sites
Posted (edited)
On 1/9/2019 at 5:43 AM, Mathwiz said:

One of my add-ons has turned out to be incompatible with multiprocess mode: the Classic Add-Ons Archive mentioned by @VistaLover not long ago. Have to disable multiprocess mode and restart in order to use that add-on. :(

Hi :) ; this is a well known and documented limitation of said extension:

https://github.com/JustOff/ca-archive#compatibility-and-installation =>

Quote

Multi-process mode (e10s) is not supported.

The author (@JustOff) is a member of the Moonchild dev team, this addon was primarily conceived to be installed in Pale Moon and/or Basilisk; the former does not inherently support electrolysis (e10s code present inside the UXP platform has been willfully crippled by Moonchild team for "application/palemoon"), while the latter does not officially support e10s (nor have any tests for it been performed with multiprocess mode turned on...).

However, the same author appears to be somehow affiliated with the Waterfox browser project, they are the ones kindly providing hosting space/bandwidth for all legacy extensions catalogued inside CAA.

Current Waterfox (a 64-bit only browser) requires Win7+, so am not in a position to try it (Vista SP2 x86 user); it comes with e10s turned ON by default, hence CAA issue #2 was submitted; the extension author came up, in v1.2.2, with a "dirty hack" to deal with e10s in Waterfox: 

https://github.com/JustOff/ca-archive/commit/a565810

What this hack in effect does is, instead of generating the

Multi-process mode is not supported now,
please disable it and restart Waterfox

pop up notification, upon clicking CAA's toolbar icon, it spawns a second non-e10s Waterfox window, where CAA can function properly (i.e. Waterfox can interpret the caa: protocol).

I have inspected the "new" code inside linked commit and, after local experimentation, have found out that implementing the same "dirty hack" for multiprocess Basilisk/Serpent is as simple as substituting the string "Waterfox" in

https://github.com/JustOff/ca-archive/blob/a5658100f67aafe1ee140545a6ab7397cdc1ec78/bootstrap.js#L169

(this is in file bootstrap.js) with the string "Basilisk":

- if (e10s && Services.appinfo.name != "Waterfox") {
+ if (e10s && Services.appinfo.name != "Basilisk") {

Be sure to first close the non-e10s window after you're done with it, i.e. simply browsing the CAA lists or having just installed something from CAA, prior to restarting the browser (to complete legacy addon installation) ...

Hope it works for you as it did for me (though I am inclined to run Serpent 52.9.0 in its default configuration, with e10s OFF => less RAM consumption :yes:)

Edited by VistaLover

Share this post


Link to post
Share on other sites

Admittedly a kludge, but it does seem to work! I can now add Classic Add-Ons Archive back to my default profile, although Markdown Viewer must remain consigned to a separate Single-process mode profile.

I'm still surprised multiprocess mode works in the first place. On my XP VM I could have just gone back to single-process mode and it would have been fine; but on Win 7 Basilisk kept freezing anytime another tab auto-updated in the "background" (until I discovered multiprocess mode works). So this kludge will still help me.

Thank goodness for 7-zip too; it makes it easy to update files (like bootstrap.js) within .xpi files (like ca-archive@Off.JustOff.xpi).

Share this post


Link to post
Share on other sites
2 hours ago, Mathwiz said:

Thank goodness for 7-zip too; it makes it easy to update files (like bootstrap.js) within .xpi files (like ca-archive@Off.JustOff.xpi).

Second that! :thumbup All the more, since, in its settings, I have configured PSPad to be the default code editor :) !

Share this post


Link to post
Share on other sites
3 hours ago, Mathwiz said:

although Markdown Viewer must remain consigned to a separate Single-process mode profile.

... Would you mind letting us know which exact Markdown Viewer extension you're using and its version?
In New Moon 28.3.0a1 I have installed (though seldom used...) the XUL (legacy) version 1.1.2 of

https://web.archive.org/web/20181102002010/https://addons.mozilla.org/en-us/firefox/addon/markdown-viewer/

Its .xpi file can be retrieved from the Web Archive, its GitHub repo and via the CAA extension discussed previously...

It can, of course, be installed in Basilisk/Serpent, but if you want e10s enabled there, you had better switched to a WebExtension equivalent, like:

https://addons.mozilla.org/el/firefox/addon/markdown-viewer-webext/

Latest v1.4.0 installs and works fine in Serpent 52.9.0 (32-bit); no way to test on official Basilisk 52, since on Vista here... Being of the WE format, it functions properly even when e10s is force-enabled in Serpent; you can test it at, e.g.,

https://raw.githubusercontent.com/KeithLRobertson/markdown-viewer/master/README.md

Regards

Share this post


Link to post
Share on other sites

Thanks! I have the legacy version, 1.1.2. I'll test 1.4.0 but I'm pretty sure it'll work since it works on @roytam1's version.

Edit: It does work. I would have been surprised if it didn't. The WebExtensions API is inherently compatible with multiprocess mode; the next question was whether Basilisk 52 supported enough of the API, but since it works on the XP build that was all but certain to be true as well.

Still, you never know about these things until you try them - especially when using an unsupported feature of the browser :o

Edited by Mathwiz

Share this post


Link to post
Share on other sites
11 hours ago, Mathwiz said:

I'm still surprised multiprocess mode works in the first place.

it does not work to me any more. I have reset everything to default settings.... :unsure:

however FF52 is working pretty well.

screenshot-3.png

Share this post


Link to post
Share on other sites

On Basilisk/UXP, when I go to Help => About, what I get is this:

about.png

Why doesn't the 'browser\VisualElements\VisualElements_150.png', which exists, get rendered over it?  :unsure:

VisualElements_150.png

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   1 member

×