Jump to content

My Browser Builds (Part 1)


Recommended Posts

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

Changelog:

Out-of-tree changes:
* update Goanna3 to git b33dced90..2a3b5ec9e:
- import change from rmottola/Arctic-Fox:
 - Bug 1141392 - Disallow a line break between ArrowParameters and the arrow. (386dac894)
 - Bug 1138651 - Enable CSS Scroll Snapping by Default on B2G. (2e416be93)
 - Bug 1140623 - Correct mochitest failures that occur when the layout.css.scroll-snap.enabled preference is enabled (V3 Patch). (cfb1ccd33)
 - Bug 1136467 - ServiceWorker: client.postMessage should land in navigator.serviceWorker.onmessage. (547bc9d03)
 - Bug 1137419 - Use correct principal for update. (9b409bd5c)
 - Bug 1137408 - Use inner window to create ServiceWorker for Fetch Event (11958cf2b)
 -  Bug 1137250 - Fix incorrect initialization of Request object. (ec637ee57)
 -  Bug 1139990 - Remove No activatingWorker warning. (49154e967)
 - Bug 1058311 - Update client interface. Implement matchAll WindowClient. (cde7ba62a)
 - Bug 1131353 - Make ServiceWorkerGlobalScope.close() throw InvalidAccessError; (0ec3f45d9)
 - Bug 1137816 - Add a test for interfaces exposed to service workers; (19b5f9504)
 - Bug 1137816 follow-up: Add WindowClient, added by bug 1058311 (ce6f0ba73)
 - Bug 1141274 - Allocate shared workers and service workers from separate namespaces; (776221d45)
 - Bug 1133763 - Part 1: Remember the security info associated with HTTP fetches and record it inside InternalResponse; (fec70ad02)
 - Bug 1133763 - Part 2: Transfer the security info associated with an InternalResponse across the IPC layer (e7192f129)
 -  Bug 1133763 - Part 3: Wipe out the cache directory when detecting a change in the DB schema; (82d81819a)
 - Bug 1133763 - Part 4: Store the response's security info in the cache database; (426e94e4b)
 - Bug 1133763 - Part 5: Allow the security info on intercepted HTTP channels to be overridden (4d079bf92)
 - Bug 1133763 - Part 6: Set the correct security info on intercepted channels when using the respondWith API (83e2b2a7d)
 - Bug 1133763 - Part 7: Add automated tests for using FetchEvent.respondWith on an HTTPS request (e0ee10e17)
 - Bug 1133763 - Part 8: Ensure that FetchEvent.respondWith works correctly on HTTPS requests with a cloned response (0db13351e)
 - Bug 1139425 - Service Worker Client uuid tests. (480b262ed)
 - Bug 1139425 - Service Worker Client id should return a DOMString uuid. (8b9ea176d)
 - Bug 1142853 - Add caret resources to package-manifest.in. (7e1a59681) (a6abc84e9)
- import change from rmottola/Arctic-Fox:
 - Bug 1132141 - Update storage when ServiceWorker registration fails. (5bf56ab4f)
 - Bug 1001691 - WorkerPrivate::LoadInfo -> WorkerLoadInfo (bc017200f)
 - Bug 1001691 - Move WorkerType out of WorkerPrivate.h (02751f7b6)
 - Bug 1131882 - Associate ServiceWorkers with underlying ServiceWorkerInfo. (4492ae042)
 - Bug 1131874 - ServiceWorker persistence activation fixes. (cd4f32309)
 - Bug 1142015 - Add source for messages dispatched to a Service Worker. (25b685a06)
 - Bug 1053275 - Exempt ServiceWorkers from per domain thread limits. (f67251f0d)
 - Bug 1139561 - Various small ServiceWorker test fixes. (dbd0beae4)
 - Bug 1130688 - Implement additional scope checking in service worker registration. (cbd8fee66)
 - Bug 1142841: Convert all nsRefPtr<nsIRunnable> to nsCOMPtr<nsIRunnable>. r=ehsan (9d4e51880)
 - Bug 1134462 - Synthesize status and headers from Response returned by ServiceWorker. (8203ae32b)
 - Bug 1134462 - allow null body. (1490bb9bd)
 - Bug 1141332 - Disable content decoding and use decoded length on intercepted channels. (2eec7968b)
 - Bug 1134330 - Mark fetch events as reloads appropriately. (a3025a42a)
 - Bug 1136757 - Add direct Response overload for FetchEvent.respondWith(). (a33248935)
 - Bug 1134462 - Cleanup Promise usage in fetch test SW. (fbe9f4cd5)
 - Bug 1134462 followup: Add missing MOZ_OVERRIDE annotation to SynthesizeStatus impls in SynthesizeStatus.h. (fb34b64d4)
 - Bug 1142124 - Never revalidate cache entries for synthesized responses. (0f4842e41)
 - Bug 1143155 - Filtered response stores internal response and allows access to headers. (956c334b1)
 - Bug 1133861 - Enable the Fetch API by default. (e05918105)
 - Bug 1140791 - Run fetch tests on main thread and workers. (e672969d6)
 - Bug 1144819 - Change JS_DefineProperty APIs to treat getter=nullptr and setter=nullptr as indicating class getter/setter ops only for data properties. (e030ab7d6) (65d6aee9e)
- import change from rmottola/Arctic-Fox:
 - Bug 1142761 - Move CallSetter into ScriptedIndirectProxyHandler so it will eventually be deleted along with its only remaining caller. (a5a0b3f6b)
 - Bug 1143810 - Remove some XPConnect JSClass::setProperty hooks that are not needed anymore. (4eda6a60b)
 - Bug 1142195 - Remove some unused class declarations in the DOM Cache code (afd802623)
 - Bug 1145345 - Account for a greater variety of rounding errors when comparing coordinates (6a41f34f3)
 - Bug 1145787 - Put a misplaced assertion into its proper place. (7f760a66d)
 - Bug 1146059 - Remove Response.finalURL. (230d9fa50)
 - Bug 1134324 - Set CORS mode and credentials on Fetch event Request. r=michal (772fcac8f)
 - Bug 1136200 - Verify request type is not no-cors if response is opaque (396c9bfb4)
 - Bug 1144249 - fix fetch no-cors mode. r=bkelly (af9656291)
 - Bug 1144876 - Stop spamming stderr with a warning every time that we encounter a document that is not controlled by a service worker; (0a5c5fbfd)
 - Bug 1117172 part 1. Allow passing an optional aGivenProto to binding Wrap methods. (8aea85046)
 - Bug 1117172 part 2. Change the non-wrappercached WrapObject methods to allow passing in aGivenProto. r=peterv (13146be83)
 - Bug 1117172 part 3. Change the wrappercached WrapObject methods to al low passing in aGivenProto. r=peterv (1621ef48d)
 - Bug 1146293 - Fix coding style break (intent and line length) caused by Bug 1117172 and Bug 1145631. (0822709f1)
 - Bug 1121298 - Part 1: refactor MozNDEFRecord cstor. (6e57a37ec)
 - Bug 1121298 - Part 2: Add Constructor(uri) for MozNDEFRecord. (46f921bcf)
 - Bug 1121298 - Part 3. add getAsURI. (e67cad94b)
 - Bug 1138886 - Structured Clone for MozNDEFRecord. (With adaptations of Bug 1117172 part 3) (b83b7f684)
 - Bug 1143504 - Disconnect the Cache object from its actor when it gets cycle collected. (dae58dcdd) (c08eaf90c)
- ported mozilla upstream change: Bug 1544386 part 1 - Call ElementAccessHasExtraIndexedProperty instead of ArrayPrototypeHasIndexedProperty when inlining array natives. r=tcampbell a=lizzard (MFSA2019-18) (eb6f09d68)
- update icu4c to 58.3 (ef31ced6c)
- clobber after icu update (614473177)
- add missing files from icu4c-58_3-data.zip (2a3b5ec9e)

* 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

Link to comment
Share on other sites


New build of Firefox 45ESR SSE:

test binary: https://o.rths.cf/gpc/files1.rt/firefox-45.9.16-20190622-73d5c57b4-win32-sse.7z

repo: https://github.com/roytam1/mozilla45esr

Changes since my last build:
- bump version to 45.9.16 (049d700ef)
- import changes from tenfourfox:
 - closes #557: M1502799 (M1526218, M1528909, M1540221, partial M1484980 with future expansion (695f6a162)
 - closes #555: shavar cryptominer auto import into adblock (also remove old 52 import script) (78e9f2e0e)
 - #559: update certs, pins, TLDs, miners (1bc40339f)
 - #561: M1544386 (apply to FPR14 for SPR1) (44e037bfb)
 - #562: ICU 56.2 sync to upstream (1fd25c510)
 - #561: cleanup (b19941fdf) (73d5c57b4)

Link to comment
Share on other sites

New build of post-deprecated Serpent/moebius for XP!
* Notice: This repo will not be built on regular schedule, and changes are experimental as usual.
** Current moebius patch level should be on par with 52.9, but some security patches can not be applied/ported due to source milestone differences between versions.

Test binary:
Win32 http://o.rths.cf/basilisk/basilisk55-win32-git-20190622-c2dfff698-xpmod.7z
Win64 http://o.rths.cf/basilisk/basilisk55-win64-git-20190622-c2dfff698-xpmod.7z

repo: https://github.com/roytam1/basilisk55

Repo changes:
- ported mozilla upstream change: Bug 1544386 part 1 - Call ElementAccessHasExtraIndexedProperty instead of ArrayPrototypeHasIndexedProperty when inlining array natives. r=tcampbell a=lizzard (MFSA2019-18) (baebe9c1a)
- ported upstream mozilla esr60 changes: bug1515052, bug1539219, bug1547757, bug1555523 (945e3a9c8)
- update ICU to icu4c-58.3, tzdata to 2019a, and marked for clobbering. (c2dfff698)

Link to comment
Share on other sites

Dave-H....Thank you very much for asking a mod to move my post,as this was where I wanted it to be in the first place..I don,t know why I have so much trouble on this particular website with my browser ...Right now I am using Safari on my IPad to post here,as my New Moon doesn’t, work correctly!.....NOW...hopefully someone can show/tell me what I need to do to fix this  very annoying “cookie” problem ...ie: settings being removed and not being saved...

Link to comment
Share on other sites

On 6/22/2019 at 6:57 PM, henry18th said:

Dave-H....Thank you very much for asking a mod to move my post,as this was where I wanted it to be in the first place..I don,t know why I have so much trouble on this particular website with my browser ...Right now I am using Safari on my IPad to post here,as my New Moon doesn’t, work correctly!.....NOW...hopefully someone can show/tell me what I need to do to fix this  very annoying “cookie” problem ...ie: settings being removed and not being saved...

ITS RIGHT HERE threads were merged. see later message

1. remove website-link from your favourites temporarily. save it elsewhere.

2. Reset Newmoon

3. remove cookies/cache(all of them)

4. remove Noscript temporarily 

5. use ccleaner i am using also regvac(only scan safe items(default).

6. defrag systempartition. i am using perfect disk, smartdefrag(beware iobit downloader will be installated in background one cannot avoid, can be removed with clamwin, maybe malwarebytes most probably Adwcleaner(quickest way).

NB: TFC(temp File Cleaner) will also be falsly detested as troyan by clamwin. clamwin the only antivirus working on my SSE-PC.
 

Edited by 3dreal
RIGHT THREAD
Link to comment
Share on other sites

On 6/21/2019 at 8:46 PM, Dave-H said:

Your original thread is only five threads below this one!
I'd already asked the mods to move it to the New Moon thread (very top of the board) because that's where it (and this one) should be.
:yes:

Cannot find. Search spitting out only this Newmoon-thread here.

Link to comment
Share on other sites

Just tested both New Moon 27 and Firefox 45 ESR SSE with the UOC Patch. They run twice as fast than the previous versions of the browsers. I also noticed that sites load faster and there's a lower CPU usage during that process. Great work, @roytam1! :)

Edited by looking4awayout
Link to comment
Share on other sites

I was recently helped by another MSFN User concerning Serpent ST55 Browser = Basilisk 55 by RT.
Concerning getting the INSTAGRAM Video (embedded) to play back properly. I was referred to this URL -->

https://msfn.org/board/topic/178259-instagram-videos-not-working-in-firefox-52-esr/page/3/?tab=comments#comment-1161357

(Note: Add this below to 'About:Config' -- Needs to be set below 56.0 for INSTAGRAM site to open)
general.useragent.override.instagram.com
(String) Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0

For myself, I had to create the Folder = "chrome" -- located inside the Folder = "Profiles"
Use (Menu) HELP , TROUBLESHOOTING INFORMATION , find "Profile Folder" , click "Open Folder" button

Then, I created the "userContent.css" file (via *.txt file first) inside Folder = "chrome" with this needed coding:

@-moz-document domain(instagram.com) {
   div.ZyFrc[role="dialog"] { display: block !important; }
}

Close Serpent ST55 Browser, reopen, and INSTAGRAM video should work properly now.
The uBlock Origin (Extension) manner (at URL above) did also succeed (work) for me too.
Figured no harm to 'repost' this information. Please give a 'LIKE' at the URL listed above if you do.

Edited by TechnoRelic
Link to comment
Share on other sites

@roytam1 It might be worth updating the thread title to something like "Goanna-based browsers by roytam1 retaining XP support", or something along those lines, since doesn't this thread also refer to KM-Goanna and Basilisk too? :P

Nice work, though! I use KM-Goanna personally since I prefer its UI over Mozilla's XUL interface, KM definitely has more of a XP-era program vibe in terms of design and layout (back when no one was forced to target social-media obsessed teenagers).

Link to comment
Share on other sites

digzu said:


It might be worth updating the thread title to something like "Goanna-based browsers by roytam1 retaining XP support", or something along those lines, since doesn't this thread also refer to KM-Goanna and Basilisk too? :P
-------------------
roytam1 said:
that's inaccurate since esr45 branch is not Goanna-based.


Instead of this big melting pot it would be SO much handier to have single topics for single browsers, as others have already mentioned too 8-)

Have also just posted something over at the K-Meleon forum, regarding KG74 crashes on 98SE and KernelEx (http://kmeleonbrowser.org/forum/read.php?19,146040,page=4), just because there is a dedicated KG74 topic. While here on MSFN it's shattered a bit everywhere, across several topics containing a multitude of different browsers, completely confusing. Although would have preferred here, far more dev experts around here. Edited by siria
Link to comment
Share on other sites

I would LEAVE this particular 'New Moon' current named 'THREAD HERE' to continue to exist.
Because @Mathwiz did FIX some of the RT Browser 'HELP' URLs to aim HERE (THIS THREAD).
And this was done, as a manner of attempting to remedy criticism from a certain 'MAT' person.
Which, now that it is done, I think that the situation is MUCH IMPROVED. I would argue
that RT can say to 'MAT' that what is REASONABLE to address the 'MAT' concerns,
has been DONE now..

As to IF that RT wants to 'monitor' ADDITIONAL MULTIPLE THREADS created
on a specific 'Unique RT Browser Defined Basis' -- SEEMS like that should be
as RT PREFERS it to be.

This 'THREAD HERE' is a bit messy, no question. But it does offer solutions and feedback
for the various RT Browsers. But okay, NOT so easy to always LOCATE the exact MESSAGE
that pertains to the specific RT Browser that you have a 'problem concern' with it.

Added Later: The TITLE of this MSFN THREAD (Here) that RT created it, is perhaps
NOT quite the best one. But again, (MSFN User) 'Mathwiz' did FIX (change) the 'HELP' URLs
in the RT Browsers to POINT to THIS RT THREAD, as CURRENTLY TITLED. And these
URL 'HELP' FIXES were done to try and satisfy concerns of a certain 'MAT' person.
So, to change this RT THREAD TITLE, would cause the 'HELP' URL FIXES
to NO LONGER open THIS RT THREAD properly (so a URL 'fail'). So, THIS RT THREAD
here is somewhat a 'NOT Broken, So Do NOT FIX IT (Change TITLE)' situation (my view).

Added Later: Amazing all that RT keeps straight in his head.

Edited by TechnoRelic
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...