Jump to content

My Browser Builds (Part 1)


Recommended Posts


20 hours ago, curiosil said:

 

How´s that? What do I need to do that?

Thanks.

1) "Easy mode": look here http://www1.plala.or.jp/tete009/en-US/software.html

2) Google for tmemutil.dll / tmemutil-3rd.dll or portable32.dll / portable64.dll and figure it out what's best for you.

Worked almost flawlessly with any mozilla-related software made last year, but probably will have problems with latest quantum-based stuff, because of multithreading and stuff. Also had some nuances with SSE2, just to mention.

The only con is probably the unhandy nature of manually patching the default dll list every time you upgrade automatically.

Link to comment
Share on other sites

On 2/3/2019 at 5:54 PM, roytam1 said:

* Notice: PM27XP builds after 20190119 may have issue with greasemonkey.

So following changes seem causing issues:

- Bug 1136925 part 1. Stop passing a parent to JS_CloneObject (02806f3cb)
- Bug 1136925 part 2. Stop passing a parent to Wrapper::New. (1d51cbd34)
- Bug 1136925 part 3. Stop passing parents to js::NewProxyObject. (dc13db8da)
- Bug 1136925 part 4. Stop passing parents to ProxyObject::New. (e2d30e340)
- Bug 1136980 part 1. Get rid of JS_SetParent uses in DOM/XPConnect. (5cad9c256)
- Bug 1136980 part 2. Remove JS_SetParent, even though we have a CLOSED TREE (96cf58c85)
- Bug 1113369, part 1 - Introduce JS::ObjectOpResult and use it in js::StandardDefineProperty. (15663c476)
- Bug 1113369, part 1½ - Avoid regressing error messages by adding obj to the ObjectOpResult methods that could throw a TypeError. (e063faf08)
- Bug 1113369, part 2 - js::SetArrayLength ObjectOpResult support. (cf8326017)
- Bug 1113369, part 3 - [[DefineOwnProperty]] ObjectOpResult support. (e16605a90)
- Bug 1113369, part 4 - [[Set]] ObjectOpResult support. (6f94604d4)

Link to comment
Share on other sites

Hey guys, I put together an installer for Roy's browsers. It checks a file on my server to see the latest version (keeping that updated shouldn't be an issue for me) and then it downloads the latest browser version from roys site and installs it.

Currently it supports Basilisk (x86 and x64), and New Moon (x86 and x64). Tested OSes with the installer include XP and Vista (both x86 and x64 editions)
 

Other builds are not currently supported due to the sometimes irregular build interval

http://i430vx.strangled.net/files/XP/RoyTam Browser Installer.exe

If you find any bugs, LMK

 

Thanks for @WinClient5270 for noticing that you must have the visual basic runtime installed first for the installer to work. (Install VC Redist 2008 from Microsoft)

Edited by i430VX
Link to comment
Share on other sites

New build of basilisk/UXP for XP!

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

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

PM28XP build:
Win32 https://o.rths.cf/palemoon/palemoon-28.4.0a1.win32-git-20190209-4adc40988-xpmod.7z
Win64 https://o.rths.cf/palemoon/palemoon-28.4.0a1.win64-git-20190209-4adc40988-xpmod.7z

Official repo changes since my last build:
- Consolidate tracing and traversing. (978f50dda)
- Remove NS_IMPL_CYCLE_COLLECTION_TRAVERSE_SCRIPT_OBJECTS (1f9ab3a6e)
- Merge branch 'master' into cycle_collector-work (1a04d73a1)
- Increase purple limit triggers for CC. (babedf6c6)
- Increase slice time for longer running CCs. (888fbacfe)
- [AM] Remove spurious warning for staged cleanup. (e4a3b28c8)
- Pale Moon: Use file path for bookmarks import/export. (aaa9fc180)
- [Pale Moon] Use mousemove events instead of MousePosTracker for hiding the navigation bar in fullscreen * Tag #336 (192715be5)
- [Basilisk] Use mousemove events instead of MousePosTracker for hiding the navigation bar in fullscreen * Tag #336 (74e88de9e)
- Fix build error with JS_HAS_TOSOURCE undefined. (f8f3dc70b)
- Merge pull request #958 from Ascrod/master (fa311a4ca)
- issue #908 - implement missing parts of CSS mask (b241a84d8)
- Merge branch 'cycle_collector-work' (9a8a05029)
- Merge pull request #961 from kn-yami/issue908 (4874970d3)
- Merge branch 'master' of https://github.com/MoonchildProductions/UXP (23f587278)
- Merge pull request #959 from FranklinDM/fullscreenpatch-v2 (5fde5ba78)
- Include blankthumb in the correct file. (f560671b6)
- Make sure Glass doesn't override LWT style for the title bar. (e05715609)
- Add "check for updates" to main menu and AppMenu (d9a054988)
- Revert "Add "check for updates" to main menu and AppMenu" (8db772d2c)
- Align `instanceof` with the final ES6 spec. (88db0108b)
- Fix possible data race while updating scope object during compacting GC. (f8db3a89b)
- Get RefPtr to transaction before using it. (DiD) (2b1ccf227)
- Never let "localhost" get sent to a proxy. (6567bb631)
- Handle pasted data of certain types with an odd length. (0b6d9a470)
- Use existing image decoders to handle clipboard BMP data. (6992106dc)
- Revert "Increase purple limit triggers for CC." (d6f995701)
- [BASILISK] Update AM preferences to point to the Basilisk Add-on Site (5c46e60ad)
- [BASILISK] Update AM preferences to point to the Basilisk Add-on Site - Part 2: Add domain to permissions file (4adc40988)

Link to comment
Share on other sites

New build of BOC/UXP for XP!

Test binary:
MailNews Win32 https://o.rths.cf/boc-uxp/mailnews.win32-20190209-95988d7-uxp-4adc40988-xpmod.7z
Browser-only Suite Win32 (removed due to request)

source patch (excluding UXP): (removed due to request)

Official repo changes since my last build:
- [PLATFORM] Update commit pointer (0358bd0)
- [PLATFORM] Update commit pointer (3903a16)
- [INSPECTOR] Use main toolbar background for modern theme (11dc15b)
- [PLATFORM] Update commit pointer (68c6dd6)
- [ABPRIME] Change menu order for Navigator (adebcea)
- [PLATFORM] Update commit pointer (0cb0749)
- [PLATFORM] Update commit pointer (e55019d)
- [MAIL] Update proxy prefpane for changes in https://github.com/MoonchildProductions/UXP/commit/6567bb631a78033b6b4cc32bc93e07d837652276 (95988d7)

For UXP changes please see above.

Edited by roytam1
Link to comment
Share on other sites

New Palemoon 27 Build!
* This build is beyond official 27.9.4 build.

32bit https://o.rths.cf/palemoon/palemoon-27.9.1a1.win32-git-20190209-7450defff-xpmod.7z
32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.1a1.win32-git-20190209-7450defff-xpmod-sse.7z
32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.1a1.win32-git-20190209-7450defff-xpmod-ia32.7z

64bit https://o.rths.cf/palemoon/palemoon-27.9.1a1.win64-git-20190209-7450defff-xpmod.7z

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

repo changes since my last build:
- import changes from rmottola/Arctic-Fox:
 - Bug 1139152: IonMonkey: Don't improve types at MTypeOf for unknown types (d67dad359)
 - Bug 994016 - IonMonkey: Improve type information at branches with TypeOf (boolean, you are worthy too) (c90a6d6fc) (d9bf24c13)
- import changes from rmottola/Arctic-Fox:
 - Bug 1138265 - TraceLogger: Throw error when trying to enable in AsmJS (64c799042)
 - Bug 1270591. Add support for checking for AVX & AVX2. Detecting AVX2 requires the use of a sub-leaf. (789319bd0) (eb895d30f)
- import changes from rmottola/Arctic-Fox:
 - update libwebp to 0.6.1 (afa956138)
 - fix build on intel for libwebp 0.6 (97193d7a0) (7174a5119)
- import changes from rmottola/Arctic-Fox:
 - Bug 1113369, part 1 - Introduce JS::ObjectOpResult and use it in js::StandardDefineProperty. (15663c476)
 - Bug 1113369, part 1½ - Avoid regressing error messages by adding obj to the ObjectOpResult methods that could throw a TypeError. (e063faf08)
 - Bug 1113369, part 2 - js::SetArrayLength ObjectOpResult support. (cf8326017)
 - Bug 1113369, part 3 - [[DefineOwnProperty]] ObjectOpResult support. (e16605a90)
 - Bug 1113369, part 4 - [[Set]] ObjectOpResult support. (6f94604d4) (74aff1670)
- import changes from rmottola/Arctic-Fox:
 - Bug 1077002 - Give a better error message when showModalDialog is used (18d8ecc12)
 - Bug 1135792. Stop assuming that every binding for a global with a non-worker descriptor is a binding for Window. (dd0260c12)
 - Bug 1135810. Add more explicit checks for whether a descriptor wants Xrays or not instead of assuming that Xrays are desired if and only if descriptor.workers is false. (17ef71544)
 - Bug 1050456 - Part 1: Prevent prerendered pages from showing the slow script dialog (173044922)
 - Bug 1050456 - Part 2: Add a nsGlobalWindow::GetIsPrerendered helper (ac680a5f7) (805fc48eb)
- reverting rmottola/Arctic-Fox changes in order to bisect memory leak and greasemonkey issue:
 - Bug 1136925 part 1. Stop passing a parent to JS_CloneObject (02806f3cb)
 - Bug 1136925 part 2. Stop passing a parent to Wrapper::New. (1d51cbd34)
 - Bug 1136925 part 3. Stop passing parents to js::NewProxyObject. (dc13db8da)
 - Bug 1136925 part 4. Stop passing parents to ProxyObject::New. (e2d30e340)
 - Bug 1130679: IonMonkey: Make it possible to guard on type changes/bailouts (ecec18313)
 - Bug 1136980 part 1. Get rid of JS_SetParent uses in DOM/XPConnect. (5cad9c256)
 - Bug 1136980 part 2. Remove JS_SetParent, even though we have a CLOSED TREE (96cf58c85)
 - Bug 1066229 - Part 5: Emitter support for basic ES6 ClassStatements. (e2a3cc979)
 - Bug 1135423 - Use unboxed objects for object literals where possible, clean up object literal creation and property initialization code (1d9e381c2)
 - Bug 1137523 part 2 - Unprefix a few js_* functions I forgot in part 1 (e6beaf0d8)
 - Bug 1135816 - Handle unboxed object receivers when compiling getter/setter calls in baseline/Ion (82233087e)
 - Bug 1138265 - TraceLogger: Throw error when trying to enable in AsmJS (64c799042)
 - Bug 1113369, part 1 - Introduce JS::ObjectOpResult and use it in js::StandardDefineProperty. (15663c476)
 - Bug 1113369, part 1½ - Avoid regressing error messages by adding obj to the ObjectOpResult methods that could throw a TypeError. (e063faf08)
 - Bug 1113369, part 2 - js::SetArrayLength ObjectOpResult support. (cf8326017)
 - Bug 1113369, part 3 - [[DefineOwnProperty]] ObjectOpResult support. (e16605a90)
 - Bug 1113369, part 4 - [[Set]] ObjectOpResult support. (6f94604d4)
 - Bug 1077002 - Give a better error message when showModalDialog is used (18d8ecc12)
 - Bug 1135792. Stop assuming that every binding for a global with a non-worker descriptor is a binding for Window. (dd0260c12)
 - Bug 1135810. Add more explicit checks for whether a descriptor wants Xrays or not instead of assuming that Xrays are desired if and only if descriptor.workers is false. (17ef71544)
 - Bug 1050456 - Part 1: Prevent prerendered pages from showing the slow script dialog (173044922)
 - Bug 1050456 - Part 2: Add a nsGlobalWindow::GetIsPrerendered helper (ac680a5f7)
 hopefully we can re-apply them later. (e1881afe9)
- re-apply rev 805fc48eb20f089ae0b815ce137bd64d6993f451 (d1c585ecf)
- re-apply rev 94617d85eb5ab3369bb44b099be3c6c4174fe6f6 (e07628294)
- re-apply following changes:
 - Bug 1130679: IonMonkey: Make it possible to guard on type changes/bailouts (ecec18313)
 - Bug 1066229 - Part 5: Emitter support for basic ES6 ClassStatements. (e2a3cc979)
 - Bug 1135423 - Use unboxed objects for object literals where possible, clean up object literal creation and property initialization code (1d9e381c2)
 - Bug 1138265 - TraceLogger: Throw error when trying to enable in AsmJS (64c799042) (7450defff)

following changes seem causing issues and they are reverted for now:
- Bug 1136925 part 1. Stop passing a parent to JS_CloneObject (02806f3cb)
- Bug 1136925 part 2. Stop passing a parent to Wrapper::New. (1d51cbd34)
- Bug 1136925 part 3. Stop passing parents to js::NewProxyObject. (dc13db8da)
- Bug 1136925 part 4. Stop passing parents to ProxyObject::New. (e2d30e340)
- Bug 1136980 part 1. Get rid of JS_SetParent uses in DOM/XPConnect. (5cad9c256)
- Bug 1136980 part 2. Remove JS_SetParent, even though we have a CLOSED TREE (96cf58c85)
- Bug 1113369, part 1 - Introduce JS::ObjectOpResult and use it in js::StandardDefineProperty. (15663c476)
- Bug 1113369, part 1½ - Avoid regressing error messages by adding obj to the ObjectOpResult methods that could throw a TypeError. (e063faf08)
- Bug 1113369, part 2 - js::SetArrayLength ObjectOpResult support. (cf8326017)
- Bug 1113369, part 3 - [[DefineOwnProperty]] ObjectOpResult support. (e16605a90)
- Bug 1113369, part 4 - [[Set]] ObjectOpResult support. (6f94604d4)

Edited by roytam1
Link to comment
Share on other sites

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

Changelog:

Out-of-tree changes:
* update troubleshoot_prefs.kmm to v17
* update Goanna3 to git 92d2d7f76..7450defff:
- import changes from rmottola/Arctic-Fox:
 - Bug 1139152: IonMonkey: Don't improve types at MTypeOf for unknown types (d67dad359)
 - Bug 994016 - IonMonkey: Improve type information at branches with TypeOf (boolean, you are worthy too) (c90a6d6fc) (d9bf24c13)
- import changes from rmottola/Arctic-Fox:
 - Bug 1138265 - TraceLogger: Throw error when trying to enable in AsmJS (64c799042)
 - Bug 1270591. Add support for checking for AVX & AVX2. Detecting AVX2 requires the use of a sub-leaf. (789319bd0) (eb895d30f)
- import changes from rmottola/Arctic-Fox:
 - update libwebp to 0.6.1 (afa956138)
 - fix build on intel for libwebp 0.6 (97193d7a0) (7174a5119)
- import changes from rmottola/Arctic-Fox:
 - Bug 1113369, part 1 - Introduce JS::ObjectOpResult and use it in js::StandardDefineProperty. (15663c476)
 - Bug 1113369, part 1½ - Avoid regressing error messages by adding obj to the ObjectOpResult methods that could throw a TypeError. (e063faf08)
 - Bug 1113369, part 2 - js::SetArrayLength ObjectOpResult support. (cf8326017)
 - Bug 1113369, part 3 - [[DefineOwnProperty]] ObjectOpResult support. (e16605a90)
 - Bug 1113369, part 4 - [[Set]] ObjectOpResult support. (6f94604d4) (74aff1670)
- import changes from rmottola/Arctic-Fox:
 - Bug 1077002 - Give a better error message when showModalDialog is used (18d8ecc12)
 - Bug 1135792. Stop assuming that every binding for a global with a non-worker descriptor is a binding for Window. (dd0260c12)
 - Bug 1135810. Add more explicit checks for whether a descriptor wants Xrays or not instead of assuming that Xrays are desired if and only if descriptor.workers is false. (17ef71544)
 - Bug 1050456 - Part 1: Prevent prerendered pages from showing the slow script dialog (173044922)
 - Bug 1050456 - Part 2: Add a nsGlobalWindow::GetIsPrerendered helper (ac680a5f7) (805fc48eb)
- reverting rmottola/Arctic-Fox changes in order to bisect memory leak and greasemonkey issue:
 - Bug 1136925 part 1. Stop passing a parent to JS_CloneObject (02806f3cb)
 - Bug 1136925 part 2. Stop passing a parent to Wrapper::New. (1d51cbd34)
 - Bug 1136925 part 3. Stop passing parents to js::NewProxyObject. (dc13db8da)
 - Bug 1136925 part 4. Stop passing parents to ProxyObject::New. (e2d30e340)
 - Bug 1130679: IonMonkey: Make it possible to guard on type changes/bailouts (ecec18313)
 - Bug 1136980 part 1. Get rid of JS_SetParent uses in DOM/XPConnect. (5cad9c256)
 - Bug 1136980 part 2. Remove JS_SetParent, even though we have a CLOSED TREE (96cf58c85)
 - Bug 1066229 - Part 5: Emitter support for basic ES6 ClassStatements. (e2a3cc979)
 - Bug 1135423 - Use unboxed objects for object literals where possible, clean up object literal creation and property initialization code (1d9e381c2)
 - Bug 1137523 part 2 - Unprefix a few js_* functions I forgot in part 1 (e6beaf0d8)
 - Bug 1135816 - Handle unboxed object receivers when compiling getter/setter calls in baseline/Ion (82233087e)
 - Bug 1138265 - TraceLogger: Throw error when trying to enable in AsmJS (64c799042)
 - Bug 1113369, part 1 - Introduce JS::ObjectOpResult and use it in js::StandardDefineProperty. (15663c476)
 - Bug 1113369, part 1½ - Avoid regressing error messages by adding obj to the ObjectOpResult methods that could throw a TypeError. (e063faf08)
 - Bug 1113369, part 2 - js::SetArrayLength ObjectOpResult support. (cf8326017)
 - Bug 1113369, part 3 - [[DefineOwnProperty]] ObjectOpResult support. (e16605a90)
 - Bug 1113369, part 4 - [[Set]] ObjectOpResult support. (6f94604d4)
 - Bug 1077002 - Give a better error message when showModalDialog is used (18d8ecc12)
 - Bug 1135792. Stop assuming that every binding for a global with a non-worker descriptor is a binding for Window. (dd0260c12)
 - Bug 1135810. Add more explicit checks for whether a descriptor wants Xrays or not instead of assuming that Xrays are desired if and only if descriptor.workers is false. (17ef71544)
 - Bug 1050456 - Part 1: Prevent prerendered pages from showing the slow script dialog (173044922)
 - Bug 1050456 - Part 2: Add a nsGlobalWindow::GetIsPrerendered helper (ac680a5f7)
 hopefully we can re-apply them later. (e1881afe9)
- re-apply rev 805fc48eb20f089ae0b815ce137bd64d6993f451 (d1c585ecf)
- re-apply rev 94617d85eb5ab3369bb44b099be3c6c4174fe6f6 (e07628294)
- re-apply following changes:
 - Bug 1130679: IonMonkey: Make it possible to guard on type changes/bailouts (ecec18313)
 - Bug 1066229 - Part 5: Emitter support for basic ES6 ClassStatements. (e2a3cc979)
 - Bug 1135423 - Use unboxed objects for object literals where possible, clean up object literal creation and property initialization code (1d9e381c2)
 - Bug 1138265 - TraceLogger: Throw error when trying to enable in AsmJS (64c799042) (7450defff)

following changes seem causing issues and they are reverted for now:
- Bug 1136925 part 1. Stop passing a parent to JS_CloneObject (02806f3cb)
- Bug 1136925 part 2. Stop passing a parent to Wrapper::New. (1d51cbd34)
- Bug 1136925 part 3. Stop passing parents to js::NewProxyObject. (dc13db8da)
- Bug 1136925 part 4. Stop passing parents to ProxyObject::New. (e2d30e340)
- Bug 1136980 part 1. Get rid of JS_SetParent uses in DOM/XPConnect. (5cad9c256)
- Bug 1136980 part 2. Remove JS_SetParent, even though we have a CLOSED TREE (96cf58c85)
- Bug 1113369, part 1 - Introduce JS::ObjectOpResult and use it in js::StandardDefineProperty. (15663c476)
- Bug 1113369, part 1½ - Avoid regressing error messages by adding obj to the ObjectOpResult methods that could throw a TypeError. (e063faf08)
- Bug 1113369, part 2 - js::SetArrayLength ObjectOpResult support. (cf8326017)
- Bug 1113369, part 3 - [[DefineOwnProperty]] ObjectOpResult support. (e16605a90)
- Bug 1113369, part 4 - [[Set]] ObjectOpResult support. (6f94604d4)

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

Edited by roytam1
Link to comment
Share on other sites

11 hours ago, i430VX said:

Hey guys, I put together an installer for Roy's browsers. It checks a file on my server to see the latest version (keeping that updated shouldn't be an issue for me) and then it downloads the latest browser version from roys site and installs it.

Currently it supports Basilisk (x86 and x64), and New Moon (x86 and x64). Tested OSes with the installer include XP and Vista (both x86 and x64 editions)
 

Other builds are not currently supported due to the sometimes irregular build interval

http://i430vx.strangled.net/files/XP/RoyTam Browser Installer.exe

If you find any bugs, LMK

 

Thanks for @WinClient5270 for noticing that you must have the visual basic runtime installed first for the installer to work. (Install VC Redist 2008 from Microsoft)

Great job!!! If it's integrated directly in prox browser builds would be fine.

I don't know if it's bug but in the old way (replacing basilisk folder with the new ones) i didn't lose anything (bookmarks and add-on) whilst with installer i lose functionality of some add-ons. For few of them disable and enable it do the trick and they come back to work but for others (like uBO 1.16.4.7) the trick doesn't work and i have to remove and reinstall it.    

Edited by Vistaboy
Link to comment
Share on other sites

6 hours ago, Vistaboy said:

I don't know if it's bug but in the old way (replacing basilisk folder with the new ones) i didn't lose anything (bookmarks and add-on) whilst with installer i lose functionality of some add-ons. For few of them disable and enable it do the trick and they come back to work but for others (like uBO 1.16.4.7) the trick doesn't work and i have to remove and reinstall it.     

I didn't notice such a thing upgrading NM on my end. (I dont have plugins installed on basilisk to test)

I don't know why it would happen

Edited by i430VX
Link to comment
Share on other sites

On 2/8/2019 at 10:27 AM, roytam1 said:

So following changes seem causing issues:

- Bug 1136925 part 1. Stop passing a parent to JS_CloneObject (02806f3cb)
...

So, is it permanent from now on or will it be reversed or patched in any future builds? In other words, is there a strong reason to stick to 01.19 builds?

Link to comment
Share on other sites

On 2/8/2019 at 8:27 PM, roytam1 said:

following changes seem causing issues and they are reverted for now:
- Bug 1136925 part 1. Stop passing a parent to JS_CloneObject (02806f3cb)
- Bug 1136925 part 2. Stop passing a parent to Wrapper::New. (1d51cbd34)
- Bug 1136925 part 3. Stop passing parents to js::NewProxyObject. (dc13db8da)
- Bug 1136925 part 4. Stop passing parents to ProxyObject::New. (e2d30e340)
- Bug 1136980 part 1. Get rid of JS_SetParent uses in DOM/XPConnect. (5cad9c256)
- Bug 1136980 part 2. Remove JS_SetParent, even though we have a CLOSED TREE (96cf58c85)
- Bug 1113369, part 1 - Introduce JS::ObjectOpResult and use it in js::StandardDefineProperty. (15663c476)
- Bug 1113369, part 1½ - Avoid regressing error messages by adding obj to the ObjectOpResult methods that could throw a TypeError. (e063faf08)
- Bug 1113369, part 2 - js::SetArrayLength ObjectOpResult support. (cf8326017)
- Bug 1113369, part 3 - [[DefineOwnProperty]] ObjectOpResult support. (e16605a90)
- Bug 1113369, part 4 - [[Set]] ObjectOpResult support. (6f94604d4)

So go ahead and try the latest version and it should be OK now.

Edited by Mathwiz
Link to comment
Share on other sites

@roytam1 <--

borealis.win32-20190126-d31e5ac-uxp-322d0be58-xpmod.7z
This above seems the last version that has the "Translate Page" option (Menu ; TOOLS - 2nd Choice Down)
With following newer versions of RT BorXP Browser, it is missing.
Was wondering IF that something 'odd' happened, and IF that "Translate Page" option could return?

Added: RT did promptly REPLY to me, next message below.
Added More: RT did eventually decide to 'Fix Restore' the "Translate Page" (TOOLS) Menu option. And has gone ahead and 'cleaned up' the BorXP Browser MENU in general. RT already did spend time to figure out how to get SeaMonkey LANGPACKS to install at a reasonable level. MORE than I did expect it. I could never have figured it out. The URL for that would be here -->
https://msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-for-xp/?page=101&tab=comments#comment-1158936

Edited by TechnoRelic
Link to comment
Share on other sites

5 hours ago, TechnoRelic said:

@roytam1 <--

borealis.win32-20190126-d31e5ac-uxp-322d0be58-xpmod.7z
This above seems the last version that has the "Translate Page" option (Menu ; TOOLS - 2nd Choice Down)
With following newer versions of RT BorXP Browser, it is missing.
Was wondering IF that something 'odd' happened, and IF that "Translate Page" option could return?

matt removed it. https://github.com/binaryoutcast/binoc-central/commit/ab39ff453746766c71ad8e37a8c2ac0a812db7bc#diff-5d439fd076db0dd17d3b7ee509bc4d48

maybe we can add it back later.

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...