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

roytam1

My browser builds (part 2)

Recommended Posts

New build of BOC/UXP for XP!

Test binary:
MailNews Win32 https://o.rths.ml/boc-uxp/mailnews.win32-20191109-6b769f4-uxp-4a0c734e1-xpmod.7z
Browser-only Suite Win32 https://o.rths.ml/boc-uxp/bnavigator.win32-20191109-6b769f4-uxp-4a0c734e1-xpmod.7z

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

There are changes in upstream now, but unless his uxp branch goes into main branch(or unless I cherry-pick his branch's changes into my tree), I will do cherry-picks of his repo only.
- cherry-picked "[Mail] Add changes to align with mailnews (096b6e0)"

For UXP changes please see above.

  • Like 1
  • Upvote 1

Share this post


Link to post
Share on other sites

New NewMoon 27 Build!

32bit https://o.rths.ml/palemoon/palemoon-27.9.7.win32-git-20191109-df039285e-xpmod.7z
32bit SSE https://o.rths.ml/palemoon/palemoon-27.9.7.win32-git-20191109-df039285e-xpmod-sse.7z
32bit noSSE https://o.rths.ml/palemoon/palemoon-27.9.7.win32-git-20191109-df039285e-xpmod-ia32.7z

64bit https://o.rths.ml/palemoon/palemoon-27.9.7.win64-git-20191109-df039285e-xpmod.7z

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

repo changes since my last build:
- bump versions (58723f645)
- ported bug1200802 (ef47f9b55)
- import changes from rmottola/Arctic-Fox:
 - Bug 968520 - Explicitly specify the allocator for nsTArray_base functions. r=froydnj (8e11c1a0c)
 - Bug 968520 - Add fallible variant of nsTArray::SetCapacity. r=froydnj (3a33bc53e)
 - Bug 968520 - Add fallible variants of nsTArray::InsertElementsAt. r=froydnj (d52030d81)
 - Bug 968520 - Add fallible variant of nsTArray::EnsureLengthAtLeast. r=froydnj (7f22637b6)
 - Bug 968520 - Add fallible variant of nsTArray::SetLength. r=froydnj (a6f43b1b0)
 - Bug 968520 - Add fallible variants of nsTArray::ReplaceElementsAt. r=froydnj (e17169b21)
 - Bug 968520 - Add fallible variants of nsTArray::InsertElementAt. r=froydnj (0ed62209a)
 - Bug 968520 - Add fallible variants of nsTArray::AppendElements. r=froydnj (c4f4d2a1e)
 - Bug 968520 - Add fallible variants of nsTArray::AppendElement. r=froydn (3fbf72f7a)
 - Bug 1165729 - Remove unnecessary template declaration for fallible nsTArray::AppendElement. r=froydnj (f72cc5efd)
 - Bug 968520 - Make nsTArray::InsertElementSorted support moves. r=froydnj (217178725)
 - Bug 968520 - Add fallible variants of nsTArray::InsertElementSorted. r=froydnj (f99e300b9)
 - Bug 968520 - Add more fallible variants of nsTArray::InsertElementsAt. r=froydnj (218d4f025) (19841f19a)
- addendum to git rev 19841f19a1e0fc573b99c2b56f280109786a79db, fix moz_malloc/moz_realloc/moz_free for our tree (3b174064e)
- import changes from rmottola/Arctic-Fox:
 - Bug 1140264 part 1 - Avoid expanding auto-hidden ruby annotations. r=dbaron (5b6ddba10)
 - Bug 1140264 part 2 - Move and merge line breaking code in rbc reflow to reduce useless computation and fix undesired break point. r=dbaron (0d3aaad79)
 - Bug 1140264 part 3 - Rename IsInlineDescendantOfRuby to ShouldSuppressLineBreak and exclude rbc/rtc from it. r=dbaron (e929b296b)
 - Bug 1140264 part 4 - Reftest for this bug. r=dbaron (3aa19d44e)
 - Bug 1141842 - Add LastOptionalBreakPriority to nsLineLayout to simplify some code. r=roc (81cc1dcd0)
 - Bug 1137875 - Have the SharedFrameMetricsData hold a copy of the layers id. r=nical (81c657510)
 - Bug 1133237 - When transitioning from a shadow layer tree that has plugins to a tree that does not, make sure the old plugins get hidden properly. r=roc (11ff16c17)
 - Bug 1137875 - Have the LayerTransactionChild hold a copy of the layers id. r=nical (f9a090aad)
 - Bug 1137875 - Clear shared frame metrics objects associated with a PLayerTransaction when it is destroyed. r=nical (c5037ee27)
 - Bug 1119878 Part 1: Change SandboxTarget to hold sandbox target services to provide functions. r=aklotz, r=glandium, r=cpearce (7378d13e4)
 - Bug 1119878 Part 2: Change IPC code to hold ProcessID instead of ProcessHandle. r=billm, r=dvander, r=aklotz, r=cpearce (fa002f559)
 - Bug 1149971 Part 1: Follow-up to bug 1119878 to fix broken IPDL tests. r=dvander (76b843d43) and some lines of fix of toolkit/xre/nsEmbedFunctions.cpp after Bug 1119878 Part 2. (5ec13acbd)
- import changes from rmottola/Arctic-Fox:
 - Revert Bug 1125848 - Consolidate PCompositor's creation-destruction logic because of 10.7 MacOS bustage (ceda5a133)
 - adapt assertion to be as introduced in Bug 1125848 (877071282)
 - Bug 1160190 followup. Make ServiceWorker actually disabled on mulet so we can reopen the CLOSED TREE. r=bkelly (1a03ee7c2)
 - Bug 1123846 - Restrict some activities to be provided by the system app r=ferjm (c7ca76805)
 - fix header include order (01b1289df)
 - Bug 1151644 - Don't disallow the basic compositor backend. r=jrmuizel (b70633afd)
 - Bug 1155823 - Properly shutdown the CompositorVsyncDispatcher. r=kats (a3dee13e8)
 - add gfxCrashReporterUtils as of 1180688  2015-07-13 (433fa6bdb)
 - Bug 1029673 - Correctly report OMTC compositing in crash reports - r=Bas (87fc22936)
 - Bug 1180688 - Detect whether the widget will be able to present frames with BasicCompositor on Mac. r=mstange (842ed309f) (eca52a3f8)
- import changes from rmottola/Arctic-Fox:
 - Bug 1125848 - Consolidate PCompositor's creation-destruction logic. r=sotaro (bd9905d37)
 - Bug 1180688 - Reset the appropriate widget states if creating a compositor fails. r=mstange (461339a0c)
 - missing part of Bug 1119878 Part 2: Change IPC code to hold ProcessID instead of ProcessHandle. (631e112dc) (df039285e)

  • Like 1

Share this post


Link to post
Share on other sites

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

Changelog:

Out-of-tree changes:
* update Goanna3 to git 13f9e7fee..df039285e:
- bump versions (58723f645)
- ported bug1200802 (ef47f9b55)
- import changes from rmottola/Arctic-Fox:
 - Bug 968520 - Explicitly specify the allocator for nsTArray_base functions. r=froydnj (8e11c1a0c)
 - Bug 968520 - Add fallible variant of nsTArray::SetCapacity. r=froydnj (3a33bc53e)
 - Bug 968520 - Add fallible variants of nsTArray::InsertElementsAt. r=froydnj (d52030d81)
 - Bug 968520 - Add fallible variant of nsTArray::EnsureLengthAtLeast. r=froydnj (7f22637b6)
 - Bug 968520 - Add fallible variant of nsTArray::SetLength. r=froydnj (a6f43b1b0)
 - Bug 968520 - Add fallible variants of nsTArray::ReplaceElementsAt. r=froydnj (e17169b21)
 - Bug 968520 - Add fallible variants of nsTArray::InsertElementAt. r=froydnj (0ed62209a)
 - Bug 968520 - Add fallible variants of nsTArray::AppendElements. r=froydnj (c4f4d2a1e)
 - Bug 968520 - Add fallible variants of nsTArray::AppendElement. r=froydn (3fbf72f7a)
 - Bug 1165729 - Remove unnecessary template declaration for fallible nsTArray::AppendElement. r=froydnj (f72cc5efd)
 - Bug 968520 - Make nsTArray::InsertElementSorted support moves. r=froydnj (217178725)
 - Bug 968520 - Add fallible variants of nsTArray::InsertElementSorted. r=froydnj (f99e300b9)
 - Bug 968520 - Add more fallible variants of nsTArray::InsertElementsAt. r=froydnj (218d4f025) (19841f19a)
- addendum to git rev 19841f19a1e0fc573b99c2b56f280109786a79db, fix moz_malloc/moz_realloc/moz_free for our tree (3b174064e)
- import changes from rmottola/Arctic-Fox:
 - Bug 1140264 part 1 - Avoid expanding auto-hidden ruby annotations. r=dbaron (5b6ddba10)
 - Bug 1140264 part 2 - Move and merge line breaking code in rbc reflow to reduce useless computation and fix undesired break point. r=dbaron (0d3aaad79)
 - Bug 1140264 part 3 - Rename IsInlineDescendantOfRuby to ShouldSuppressLineBreak and exclude rbc/rtc from it. r=dbaron (e929b296b)
 - Bug 1140264 part 4 - Reftest for this bug. r=dbaron (3aa19d44e)
 - Bug 1141842 - Add LastOptionalBreakPriority to nsLineLayout to simplify some code. r=roc (81cc1dcd0)
 - Bug 1137875 - Have the SharedFrameMetricsData hold a copy of the layers id. r=nical (81c657510)
 - Bug 1133237 - When transitioning from a shadow layer tree that has plugins to a tree that does not, make sure the old plugins get hidden properly. r=roc (11ff16c17)
 - Bug 1137875 - Have the LayerTransactionChild hold a copy of the layers id. r=nical (f9a090aad)
 - Bug 1137875 - Clear shared frame metrics objects associated with a PLayerTransaction when it is destroyed. r=nical (c5037ee27)
 - Bug 1119878 Part 1: Change SandboxTarget to hold sandbox target services to provide functions. r=aklotz, r=glandium, r=cpearce (7378d13e4)
 - Bug 1119878 Part 2: Change IPC code to hold ProcessID instead of ProcessHandle. r=billm, r=dvander, r=aklotz, r=cpearce (fa002f559)
 - Bug 1149971 Part 1: Follow-up to bug 1119878 to fix broken IPDL tests. r=dvander (76b843d43) and some lines of fix of toolkit/xre/nsEmbedFunctions.cpp after Bug 1119878 Part 2. (5ec13acbd)
- import changes from rmottola/Arctic-Fox:
 - Revert Bug 1125848 - Consolidate PCompositor's creation-destruction logic because of 10.7 MacOS bustage (ceda5a133)
 - adapt assertion to be as introduced in Bug 1125848 (877071282)
 - Bug 1160190 followup. Make ServiceWorker actually disabled on mulet so we can reopen the CLOSED TREE. r=bkelly (1a03ee7c2)
 - Bug 1123846 - Restrict some activities to be provided by the system app r=ferjm (c7ca76805)
 - fix header include order (01b1289df)
 - Bug 1151644 - Don't disallow the basic compositor backend. r=jrmuizel (b70633afd)
 - Bug 1155823 - Properly shutdown the CompositorVsyncDispatcher. r=kats (a3dee13e8)
 - add gfxCrashReporterUtils as of 1180688  2015-07-13 (433fa6bdb)
 - Bug 1029673 - Correctly report OMTC compositing in crash reports - r=Bas (87fc22936)
 - Bug 1180688 - Detect whether the widget will be able to present frames with BasicCompositor on Mac. r=mstange (842ed309f) (eca52a3f8)
- import changes from rmottola/Arctic-Fox:
 - Bug 1125848 - Consolidate PCompositor's creation-destruction logic. r=sotaro (bd9905d37)
 - Bug 1180688 - Reset the appropriate widget states if creating a compositor fails. r=mstange (461339a0c)
 - missing part of Bug 1119878 Part 2: Change IPC code to hold ProcessID instead of ProcessHandle. (631e112dc) (df039285e)

* 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 2

Share this post


Link to post
Share on other sites

@3dreal said:


so i must surf to palemoon-folders which will be changed after every update? i am extracting updates into seperate folders. as i said installer non-working.
will first install patch for FF 45ESR where i didnt yet patch UOC. and remove the wrong one beforehand in Palemoon-folder. i have a FF-folder in Programme but its from earlier FF-installations. So where to install the patches? yes i know the workaround but must run FF and PM outside programs aka programme-folder.


Whoah.... your stories are real drama!
And the above sounds like you're not too aware what you're dealing with here, but it's not quite trivial. I think it's all described in detail on the first UOC page, and strongly recommend studying it. But it's been a while that I've read it myself, so just a few quick tips from my own understanding: What matters most, is to FIRST make a backup of your profile! Or at the very least of PREFS.JS and USER.JS (if existing). You will need those files again to restore your current settings if later you remove the patch again. You can find your current profile folder in a link on the about:support page. IIRC the enforcer file goes into that profile folder, contents to be added in user.js, but better read this in the instructions to be sure. The "normal" patch file creates different "default" values for the contained prefs. This file goes into your unzipped program folders, into subfolder ../defaults/pref/ or /defaults/preferences.

You want new profiles? Regarding K-Meleon, if you use roytam's 7z build, those create the profiles inside the unzipped program folder. You can just delete that "profiles" folder and restart, but I recommand to keep the current profile and just create a second one:
Menu Edit>Manage Profiles
K-Meleon also has the specialty that some user settings are stored outside of the profile, especially when changing toolbars, but you don't sound like you customized very deeply.

PS: your screenshot, is it really intentional that you have the file types hidden, the endings after the filenames?? Or only because it's that stupid MS default setting? At any rate that icon for UOC looks you did not unzip the patch yet, that means it simply got ignored. You must extract the contained files to do anything with them.
  • Like 1

Share this post


Link to post
Share on other sites

i am now on FF 45 ESR-working FB slow. one can say stable till now.
Update: PM 27-SSE + FB
Hurrah-FB seems to have found out they made a mistake. i can surf the site. nothing covered also here.but a bit slow FB .its 6AM in europe.

it all(capacitor plague on both open PCs) started mid-june 2018-one month before my fathers(96) death.good i visited him a last time days before but was busy for weeks.
Both are universal SATA-IDE-MOBOs. and i still like asrock. WAs was on ASROCK with Win7 when suddenly booting was not possible anymore pc like dead. i know this kind of problem and workarounds. often cleaning contacts helped but also resoldering electrical points and replacing battery-case. Open MOBOs and a lot of cables touched by my left leg were nothing positive.
I know both PCS now byheart. I could reactivate both then concentrated on the older GA since i needed a backup-pc anyhow. Even thought about establishing two identical ones. but both are slow and few space here.
Yes will now study the pref-and UOC-PATCH thing. But help is needed since i cannot install these browsers. but i will retry.
Where should i find the profiles to backup?

Edited by 3dreal
good news reg. FB and PM 27SSE

Share this post


Link to post
Share on other sites

Re-downloaded moebius and recaptcha is coming in but most of the time the play option gives me the “Your computer or network may be sending automated queries” message. There’s v2 and v3 recaptcha and the newer firefox probably calls v3 where the play option almost never fails.

Roytam, there’s one minor issue with moebius, the pref “mousewheel.with_control.action” doesn’t affect horizontal scroll when set to 4. In UXP this functions properly as it does in every other version of firefox. Can it be fixed?

Share this post


Link to post
Share on other sites
12 hours ago, DanR20 said:

there’s one minor issue with moebius, the pref “mousewheel.with_control.action” doesn’t affect horizontal scroll when set to 4. In UXP this functions properly as it does in every other version of firefox. Can it be fixed?

will have a look later to see if I can fix it or not

Share this post


Link to post
Share on other sites

Hello everyone, haven't been here for 6-8 months, so I have 2 questions. Help me please =)

1. What is the difference between 27.9.1 and 27.9.18 versions of PM from the 1st page of this new thread? I'm currently using 27.9.6 version for XP (2019-03-23).

2. Some modern sites have JavaScript errors. For example, code snippets with syntax highlighting and diff support on emberjs.com don't work in PM 27.9.6, but work perfectly in Firefox 52.9.0 ESR portable. The question is will this problem be fixed by updating to latest 27.9 build, or should I use 28.x instead? Is the JavaScript engine getting updates regularly, or only security and performance patches are applied by @roytam1?

The code that is breaking for me is

var e = this.element.querySelectorAll('pre:not(.no-line-numbers) > code')
e && e.forEach(function (e) {
    e.parentNode.classList.add('line-numbers')
})

I know what's happening here, it's just the laziness of programmers who didn't bother to call [].slice.call(e).forEach instead of just e.forEach, that is, I suppose, allowed by newer standard. I have seen it on another site before.

Anyway, is it already fixed in 27.9, which I love for its speed, or will it never be?

Edited by Alex654

Share this post


Link to post
Share on other sites

Just stopped in to say thank you very much for keeping these browser forks updated and working well. A number of web sites are starting to turn their nose up at 27.9, but with the other two, I can still get to where I must on Windows XP. Although I hate how Mozilla messed up the title bar/menus in 52/Basillisk.

Noticed that this moved to a new thread on the forum - you guys really need an entire subforum dedicated to this. :)

Thanks!

  • Like 2

Share this post


Link to post
Share on other sites

Thinking back about the time when "you know who" made a lot of fuss about the branding of the forked browsers, I noticed mainstream Basilisk still contains strings where the browser is referred to as "Firefox".

  • Like 2

Share this post


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

CTR is still available outside of the CAA extension (which is where you obviously obtained that direct link from ;) ) in the author's GitHub repository:

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

If you're using the official Basilisk application on Win7+, then the latest CTR_v1.7.8.2019.10.27 is recommended; if, OTOH, you're using Serpent 52.9.0/55.0.0, then CTR_v1.7.8 is the last (EoS'ed) version for Serpent; the add-ons manager (AOM) is now different between Bk and St (Bk now uses PM's AOM with no support for WEs, while St retains FxESR52's AOM), Aris is currently maintaining CTR for official Bk (and classic Waterfox), only... :(

Share this post


Link to post
Share on other sites

Notice: git repo update times may be decreased as I need more time on transportation to/from workplace at the moment. #5DN1L

  • Upvote 3

Share this post


Link to post
Share on other sites
On 11/9/2019 at 5:36 PM, DanR20 said:

as it does in every other version of firefox.

(The discussion topic here is horizontal scrolling via mousewheel )

Hi :) ; most members frequenting this thread are on Windows XP (or older OSes), with the exception of the few Vista users like me; not all of such members have ready access to Win7 or higher... :(

I tested several Firefox versions (up-to-and-including v53) that would run in my system, I wasn't able to enable HS in any of them, via either of the following "mousewheel.with_*.action" prefs:

mousewheel.with_control.action;4
mousewheel.with_shift.action;4

It turns out that HS was enabled in Firefox only as recently as v58.0:

Horizontal Scrolling with Mouse wheel+ modifier key

and, mind you, that was a bug originally opened in 2002 (!) ...

Mercurial commit that implemented the fix:

https://hg.mozilla.org/mozilla-central/rev/63b547bb4078

So, pray tell, which was "every other version of firefox" ?

On 11/9/2019 at 5:36 PM, DanR20 said:

In UXP this functions properly

Actually, that's quite an interesting story...

Horizontal scrolling had been implemented in a perfect way by MCP in the previous PM platform, Tycho, forked off Mozilla ESR 38; New Moon 27.9.x, currently maintained by @roytam1, is built on Tycho ;) ; HS in Tycho can be enabled by setting one of the "mousewheel.with_*.action" prefs to a value of 4.

HS in Tycho works on both pages and frames; to test it on a page, zoom the page content until a horizontal scroll bar appears in the bottom of the tab; keep the designated key pressed and by simply moving the mousewheel, that bar should move, too...

To test on a frame, just load https://www.bing.com in a tab and then have the bookmarks/history sidebar displayed (e.g. ctrl+B); increase the sidebar's width to the right, so that a horizontal scroll bar appears in the bottom of the bing tab...

When PM was ported from Tycho to UXP, that feature (HS) regressed :realmad: :

https://forum.palemoon.org/viewtopic.php?f=37&t=20119 =>

https://github.com/MoonchildProductions/UXP/issues/732 =>

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

However, Moonchild's fix was only partial, in that HS works in PM/NM28 for pages only, not frames; relevant UXP bug is still open: 

https://github.com/MoonchildProductions/UXP/issues/1173

On 11/10/2019 at 5:52 AM, roytam1 said:
On 11/9/2019 at 5:36 PM, DanR20 said:

there’s one minor issue with moebius, the pref “mousewheel.with_control.action” doesn’t affect horizontal scroll when set to 4. (snipped) Can it be fixed?

will have a look later to see if I can fix it or not

What you can obviously do is try whether UXP bug 732 (linked to above) applies cleanly in Moebius; of course, it would be just as partial, i.e. only apply on pages... IDK whether Mozilla bug 143038 is a better approach to the issue at hand... :dubbio:

FWIW, legacy extension "Shift + Scroll (Horizontal Scrolling)" is available via CAA ("caa:addon/shift-scroll", originally over at AMO ); not tested :P ...

 

Edited by VistaLover
  • Like 1

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.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...