Leaderboard

@Sampei.Nihira suggested changing the cipher suites into something other than the standard ones. It isn't what anyone who wants to just blend in with the crowd wants to do. I use Cent browser, and it has a fingerprint of the standard Chrome.

Ok. I was able to improve a bit my custom button for calling up the "Manage Cookies and Site Data" window. Both, the about:preferences#privacy and three seconds later the desired dialogue are now loaded in the same chrome window which avoids an additional loading of a tab. Nevertheless, I hope that there is a better solution yet.

Xper, thank you for taking the time, it's not always with us, it's on and off. As of lately, it again went to normal with the last wave of spammers, I'm not joking. Or maybe it has something to do with links adding issues people reported earlier. Or PMs. https://msfn.org/board/topic/185994-cant-edit-my-first-post-in-thread-error-when-posting-links/ https://msfn.org/board/topic/186314-issues-with-the-board-personal-messages/ P.S. Probably the title needs to also include the inability to post cmd. exe (without the space), as I discovered recently.

Long pause before the posting is done came back.

No assumptions at all, it's what you wrote yourself, read above, all in capslock. Two or three daily poor spammers seem excessive to you, come on, really?

I don't think so, what if I wanted to write I'm against using cracks, or tell it may even be unsafe? What then? What you suggest is called censorship, and I don't live in a place without the free speech rights.

Dear Xper. I need to report a serious issue that can't be made publicly without violating the rules. Is there a way to establish a hot line for this one-time reporting? Again, I would never bother if it wasn't that serious. Thanks for understanding.

I have zero problems with reporting bots, just like @Tripredacus once told me to do. It doesn't bother me at all, in a huge contrast to you. I even find them a bit funny, sometimes. The ones that were selling ego-boosting potions, for example.

No, this wouldn't be different on any SAB version. This is not an error popup either.

I did contact BE. But I don't believe it's an even minor level problem as it does not disrupt anything. Close BE window and that is it.

... Possibly slightly off-topic here, but I, too, was using above userscript (in Violentmonkey, in Serpent 52) ; it used to work on both the (bloated) desktop YT GUI and the mobile YT GUI, too (via that Fx WE) ; well, the userscript can be now considered "a thing of the past", as a result of the ruthless war Google unleashed against YT-specific scripts/extensions/downloader apps, etc. A month or so ago Google changed radically the way their fragmented streams (MPEG-DASH) are being delivered to "web" clients (browsers); each fragment is now "POST-requested" instead of "GET-requested" and, additionally, each fragment URI is now being "protected" by a PO (point-of-origin) token, unique to the browser YT session; that change alone BROKE practically all downloader usercripts for browsers (e.g. Youtube Links) and SYTARB suffered the same blow, in that adaptive age-gated streams were impossible now to "unblock"; to add insult to injury, Google have also removed the most popular "progressive download" format 22 (premuxed, standalone MP4 container with h264@720p25+aac@128k), so the userscript could, at best, unblock just the lowly format 18 (progressive, h264@360p25) ... However, it appears that even that is now out of reach, because the "age-verified-YT-account-proxy", the back-bone of the userscript (and of a specialised yt-dlp plugin) has been taken DOWN ca. 2wks ago (supposedly the hosting agreement expired ); you can read more at the userscript's GitHub issue tracker ; with Google even patching the only known "hack" (tv_embedded client) to bypass age-gated videos, it's now IMPOSSIBLE to view/download age-restricted YT videos without an age-verified YT account... I have never had a Google account myself and I'm not inclined on creating one now just for the sake of watching those age-gated clips (which, due to "political correctness", have grown exponentially in their numbers; yet another Google ploy to grab your personal details, if you ask me); in my country (EU member), the last time I checked, Google wanted to send them a digital scan of your "proper" ID card so that they could "age-verify" your YT account ... The web, just like the real world, has turned into a really "bad place" - I'm despaired/depressed by both, TBH ...

StartAllBack 3.8.12

@feodor2 Calling up chrome://browser/content/preferences/siteDataSettings.xul directly does not show the most recent cookie database. When calling up the about:preferences page beforehand, the most recent cookie database is shown, and the XUL file call works again correctly. Do you know how to do in JavaScript the same what calling up the about:preferences page does in terms of the cookies? I need the part of the code that is executed by the call to the about:preferences page regarding cookies before I call up the chrome://browser/content/preferences/siteDataSettings.xul file. As I mentioned, I am in the process of creating a Cookie Button which opens the dialogue "Manage Cookies and Site Data". My current version automatically opens the about:preferences#privacy page and three seconds later the wanted dialogue in an own chrome window. This indeed works properly but actually I would like to avoid opening an about:preferences#privacy tab by doing the necessary commands internally via JavaScript. I already tried a lot but without any success. So, any ideas?

Ok. I understand that very well. Completing the new version is a much higher priority. But one thing is clear. A bug is a bug. Or call it an issue, an unwanted behaviour or whatever. Regardless of whether you don't consider it important or don't want to fix it. Calling the cookie GUI via its XUL file directly is faulty. I have investigated and documented it in detail. The script is the same, it is heavy obfuscated and refuses to work too if to block the connection to its site, very suspicious so not suitable. No need to block its connection. The script is simply great. Sometimes, one has to trust. Without trust you can't do anything when using software, scripts and similar made by others. Would be great to have document.loadOverlay() back in Mypal 68.

A new version of Supermium came out since yesterday! https://github.com/win32ss/supermium/releases/tag/v126-r4 @Dave-H Yes, your feature request has been added!

@feodor2 The non-standard JavaScript function document.loadOverlay() is deprecated since Gecko 60 (Firefox 60). Did you completely remove it in Mypal 68? Some of my (important) scripts call up this function which leads to the error message "TypeError: document.loadOverlay is not a function" in the Browser Console. If it has been removed, can it be re-implemented? I ask this as in more recent Firefox versions, these problematic scripts seem to be working again which means the document.loadOverlay() method is there again and works.

Hope you can fix this bug. If it was fixed, my self-created custom button would work as I planned without any special workaround to be implemented. I use the VORAPIS V3 script version. Works great here in Mypal 68.

@feodor2 Thanks for the links! The history feature of GitHub is great. Thanks to @UCyborg's hint to use this time machine, I started downloading repositories from the Firefox 68 era. With the linked version of xiaxiaofloods's userChromeJS, you can indeed install bootstrapped, legacy extensions in Mypal 68, but unfortunately, none of xiaxiaofloods's extensions I've tested from the linked repository do actually work.

Surely this is unsolvable? GTA Online works fine but this popping up can be annoying.

@feodor2 I noticed this issue when creating a custom button for calling up the cookie manager. For reproducing this issue, call up chrome://browser/content/preferences/siteDataSettings.xul, delete a site cookie of your choice, close it, open the site whose cookie you deleted and call up chrome://browser/content/preferences/siteDataSettings.xul again. You will then notice its cookie is not listed although it is there. And when now restarting the browser, the call up of this internal chrome site leads to an empty, broken and non-functional interface. Here is a screenshot of this issue including the TypeError message Uncaught TypeError: this._getQuotaUsagePromise is null SiteDataManager.jsm:255:5 getSites resource:///modules/SiteDataManager.jsm:255 init chrome://browser/content/preferences/siteDataSettings.js:127 onload chrome://browser/content/preferences/siteDataSettings.xul:1 in the Browser Console: Only by calling up the about:preferences page will it work again. BTW, when doing so in an UXP browser as, for example, New Moon 28 or Serpent 52 by calling up chrome://browser/content/preferences/cookies.xul, there is no such problem.

@feodor2 When calling up the internal site chrome://browser/content/preferences/siteDataSettings.xul in Mypal 68.14.4b directly, the list of all cookies is not up to date in most cases. Only when you call up the about:preferences page beforehand, you get a current list of all cookies. Actually that can't be the intention. Right? So, is this a bug or really by design? When calling up the internal site chrome://browser/content/preferences/siteDataSettings.xul directly after browser restart, it is empty, broken and non-functional.

I have spent the last few days testing Mypal 68.14.4b with heavy and resource-hungry websites and have come to the conclusion that old, heavily modified profiles with many extensions, userscripts and CSS stylesheets installed do not work well with sites such as eBay, Amazon or Discord. With a new, fresh profile, in which only the most necessary settings are made, these sites run much better.

I can't confirm your statement. VORAPIS V3 works perfectly on my very old Windows XP computer. I simply installed it without any special settings. Very, very fast and responsive frontend, resource-friendly and fully functional video playback. Have a look at here: https://msfn.org/board/topic/183657-mypal-68-in-windows-xp-custom-buttons-and-extensions/?do=findComment&comment=1273034

I downgraded the browser to 116 from 119 Chrome, MSFN now works very good!

I think it makes no sense to test ordinary and simple words. Those that have problems are usually tech. terms.

_isdel.exe

AdapterTroubleshooter.exe

And which exactly (hence one word postings).

It's simply not funny and very spammy. People are trying out to find out why those technical terms like cmd .exe are blocked, please don't interfere.

DFDWiz.exe

Defrag.exe

cmdl32.exe

thanks for reporting! a fix is landed in custom branch, and will be available in next build.

I think it needs to revert/readd XP support in order to work for our needs.

New NewMoon 27 Build! 32bit https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20210925-45e41b763-xpmod.7z 32bit SSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20210925-45e41b763-xpmod-sse.7z 32bit noSSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20210925-45e41b763-xpmod-ia32.7z 64bit https://o.rthost.win/palemoon/palemoon-27.10.0.win64-git-20210925-45e41b763-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import changes from `dev' branch of rmottola/Arctic-Fox: - missing bit of Bug 889158 - Fix arrow function lexical arguments binding (6dd07824a) - missing parts of Bug 1135708 - Implement es7 exponentiation operator. (87d1b2a09) - Bug 1183400 - Add a by-kind switch to perform constant-folding and eventually eliminate by-arity handling. r=efaust (ce6768404) - Bug 1171909 - Check for alloc failure initializing AssemblerBufferWithConstantPools and update error handling ExceptionHandlerBailout r=jandem (fb86a97ec) - Bug 1182428 - Consider TypeSet stuff to be GCPointers, since they can contain them, r=jonco (2a7841983) - Bug 1184199 - Use a Map instead of a plain object to avoid the "constructor" property, r=jonco" (3af559983) - Bug 1184199 - Add an explanation only if there is something to explain, r=jonco (882178fcf) - Bug 1182428 - Improve naming, r=jonco (24bcf0679) - Bug 1182428 - Recognize more rooted type names, r=jonco (75e9d692e) - Bug 963738 - Assume(ptr) is not a hazard; Assume(*ptr) is, r=bhackett (e704d13e6) - No bug. Add a --function argument for analyzing a single function by name. (d9e8fc4c0) - Bug 1172682 - Comment and refactor analysis code, r=terrence The one change this patch makes in functionality is that it properly computes minimumUse in more cases, in anticipation of it being used for hazards (in addition to its current use for unnecessary roots). (a481f942a) - Bug 1182428 - Accept more edge types in edgeCanGC, r=jonco (98413c47f) - Bug 1170200 - Part 1: Change the API for nsIPermissionManager::Remove() to accept a URI instead of a string; r=ehsan (bd5ef47ed) - Add two missing includes to SharedMemoryBasic_mach.cpp, no bug (dbdeeaca1) - bug 1175898 - crash in mozilla::CrossProcessMutex::ShareToProcess(int) r=billm (93cab5830) - bug 1204985 - make SharedMemoryBasic_mach build on iOS. r=billm (0f7b668c3) - bug 1204985 horrible clobber-avoidance bustage fix r=YOLO CLOSED TREE (d46b9b946) - Bug 1205164 - Detect message races in Mach Shmem implementation. r=blassey (2b88cc22b) - Bug 1221540: OS X IPC timeout retry with a longer interval. r=milan (66d2006fe) (9e300313d) - import changes from `dev' branch of rmottola/Arctic-Fox: - bug 1167604 - don't hide ProxyAccessible::Parent() with DocAccessibleParent::Parent r=lsocks (32e4cac18) - Bug 1173418 - Check if a document is top level in DocAccessibleParent::Destroy so that RemoteDocShutdown isn't erroneously called r=tbsaunde (db280c0a1) - bug 1184217 - check consistancy of the document tree before removing accessibles in a hide event r=davidb (91d2f38fb) - bug 1162543 - make DocAccessibleChild::IDToAccessible correctly get the document r=davidb (be2eb3eb7) - bug 1170595 - switch to sending __delete__ from the parent instead of the child r=davidb, smaug (216a90d34) (3a8ef50a8) - import change from `dev' branch of rmottola/Arctic-Fox: - MOZ_OVERRIDE -> override (624f7c712) (57cc49827) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1182373 - Don't constant-fold in the tag component of a tagged-template, because constant-folding evaluates the tag too early (and moght convert a value into a property reference, causing the wrong |this| to be passed). r=jorendorff (f9e41352b) - Bug 1183400 - Constant-fold nullary nodes entirely according to their kind, not their arity. r=efaust (9c6248dd8) - Bug 1183400 - Fold typeof nodes by examining their kind. r=efaust (0dc443122) - Bug 1183400 - Fold |void <expr>| expressions by kind. r=efaust (d872286ad) - Bug 1183400 - Fold delete nodes by kind. r=efaust (a30634947) - Bug 1164774 - Remove unused code handling binary-arity PNK_ADD nodes in constant-folding. r=shu (996db297b) - Bug 1183400 - Fold !/~/+/- by kind. r=efaust (bf5dd5984) - Bug 1183400 - Pass a Parser reference to Fold, not separate handler/options, preparing for another patch that wants to have access to a parser instance. r=efaust (5bbb167be) - Bug 1183400 - Fold increment/decrement operations by kind. r=efaust (2728e23a7) - Bug 1183400 - Fold ?: expressions by kind. r=efaust (64d6ab853) - Bug 1183400 - Fold |if| nodes by kind. r=efaust (0f701a6bb) - Bug 1183400 - Fold various simple unary cases by kind. r=efaust (590b24acb) - Bug 1183400 - Fold and/or expressions. r=efaust (1f114d2b2) - Bug 1183400 - Fold function nodes by kind. r=efaust (0920010c0) - Bug 1183400 - Fold binary arithmetic operations by kind, not arity. r=efaust (a3723a1ec) - Bug 1183400 - Remove a now-unused variable, following up on the ?:/if-node folding changes. r=trivial, r=orange in a CLOSED TREE (522584dc0) - Bug 1183400 - Inline FoldBinaryNumeric into its sole caller and simplify code accordingly. r=efaust (043ccf349) - Bug 1183400 - Fold various list nodes not given, nor requiring, special treatment. r=shu (7de28f276) - Bug 1183400 - Constant-fold yield/yield*/return by kind and not arity. r=shu (7cae87421) - Bug 1183400 - Fold try/catch by kind. r=shu (5df2a97fc) - Bug 1183400 - Fold class nodes by kind. r=shu (67fffcc45) - Bug 1183400 - Fold element accesses by kind. r=efaust (82538a7a2) - Bug 1183400 - Fold addition by kind. r=efaust (68a0c6b49) - Bug 1183400 - Fold function calls and tagged templates by kind, not arity. r=efaust (0a368e8f9) - Bug 1183400 - Fold various binary nodes with two non-null halves by kind. r=efaust (de48c675b) - Bug 1183400 - Fold while and do-while loops by kind, not arity. r=efaust (998bd13cc) - Bug 1183400 - Remove dead fold-by-arity code. r=efaust (3b5f719b9) - Bug 1183400 - Remove SyntacticContext::Delete, now addressed by modifying how delete nodes are folded. r=efaust (8129f5f7c) - Bug 1183400 - Constant-fold switch/default by kind, not arity. r=efaust (e9430d603) - Bug 1183400 - Fold for-in, for-of, and for(;;) loops by kind, and classify miscellaneous straightforward kinds for folding. r=efaust (59d09a110) - Bug 1183400 - Replace callee-based condition-constant folding with caller-specified condition-constant folding. r=efaust (2090ea750) - Bug 1183400 - Remove special |void| handling by making Boolish recognize |void| expressions as falsy, when they're obviously so. r=efaust (d230cbb0d) - Bug 1183400 - Remove SyntacticContext::Condition, now handled context-sensitively by callers specifically requesting condition-targeted folding. r=efaust (8be79cd7a) - Bug 1183400 - Fold the last few nodes (including PN_NAME nodes) by kind, not arity. r=efaust (4e8e911a4) - Bug 1183400 - Remove SyntacticContext completely. r=efaust (745d4df15) - Bug 1183400 - Common up some is-effectless testing. r=efaust (ed25885e6) - Bug 1135322 - receiveMessage() should convert logins to nsILoginInfo objects. r=MattN (35da0f066) - Bug 1140242 - Convert nsILoginInfo to vanilla JS objects before trying to send them in messages. r=dolske (f952e9ab5) - Bug 1134846 - Add a module to support per-site password manager recipes. r=dolske (d9d686818) - Bug 1135451 - fillForm() cleanup part A: remove unused return type, kill E10S unfriendly fillForm from nsILoginManager, kill passwordmgr-found-form notification, largely a backout of bug 439365. r=MattN (3825eb1dd) - Bug 1120129 - Allow per-site recipes to adjust the username/password field detection for autofill. r=dolske (423202980) - Bug 1144981 - username/password recipe for www.anthem.com. r=mattn (55ce95a2b) - Bug 1146065 - Logins captured but not filled on discover.com. r=mattn (4b19c1a01) - reorder after strange misspatch (706cfd4ea) - Bustage fix for bug 1146065. (4b0a7b5f6) - fix some mispatches and also put back some "backports" lost with Bug 1182969 (f61e63baf) (45e41b763) -- ffmpeg library lite 3.4.9 for NM27/KMG76: 64bit https://o.rthost.win/palemoon/lav64-dll-lite-3.4.9.7z 32bit https://o.rthost.win/palemoon/lav-dll-lite-3.4.9.7z 32bit nosse https://o.rthost.win/palemoon/lav-dll-lite-ia32-3.4.9.7z 32bit noasm https://o.rthost.win/palemoon/lav-dll-lite-noasm-3.4.9.7z

Moon Tester Tool can be used by a monkey to install an extension if its only issue is that it doesn't target Pale Moon. In either case, all extensions come in a form of .xpi file (basically ZIP archive) which contains text install.rdf file, containing basic information about the extension such as GUID, name, version, which applications it targets etc. The Moon Tester Tool basically rewrites the file so the extension targets Pale Moon. Information about the max version of the target application is ignored unless strict compatibility checking directive is present/enabled. Some extensions contain the directive that the XPI content should be extracted upon installation, for these extensions you should find the original XPI file. AFAIK, New Moon still accepts extensions targeting Firefox, so if some extension doesn't work, parts of its logic may have to be rewritten to accommodate for changes in the browser core. I supposed you'd have to find the old documentation for XUL coding and info regarding whatever MCP folks changed that broke the extension to be able to fix, the developer tools baked in the browser may also give hints. I modified Destroy The Web some time ago to remove dependency on deprecated FUEL, which is long gone from Basilisk and will eventually disappear from Pale Moon as well.

you may check this out: https://archived.moe/g/thread/83419847/#83435476

should be fixed

save this as google.xml and put it in <newmoon-application-folder>\browser\searchplugins: <!-- This Source Code Form is subject to the terms of the Mozilla Public - License, v. 2.0. If a copy of the MPL was not distributed with this - file, You can obtain one at http://mozilla.org/MPL/2.0/. --> <SearchPlugin xmlns="http://www.mozilla.org/2006/browser/search/"> <ShortName>Google</ShortName> <Description>Google Search</Description> <InputEncoding>UTF-8</InputEncoding> <Image width="16" height="16">data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAMAAAAoLQ9TAAABF1BMVEUAAAD////+/v7////+/v7////+/v79/f39/f39/f39/f39/f39/f39/f39/f39/f39/f39/f39/f39/f39/f39/f00qFM4qlY6qlg6q1hBhvBChfRGh/RIqktKo5lXt3FYr45Yt3FZuHJdunZnnfZ1pvd7qveCrviNtfiR0KKb1Kqd1ayn2bSw0Y3D2PzM6dTN1onO6tXO6tbY5v3o8P7p9ezqQzXqRjjqRzrrSTvrSjzsUjftXlLtYlbtvBHuY1juZlruaV3wdmzxxCz0nJX0nZb1qaL2pGv2rKX2+/j5sgr5/Pr5/fr60s/61ND61NH7vAX7vQr7vgv7z5L8yTX84+H96uj+67X+7Lb++fn+/v///f3///9G7xLpAAAAFnRSTlMACAkKLjAylJWWmJmdv8HD19ja2/n6GaRWtgAAAL9JREFUGBk9wIVawlAAhuGfwYgdRGJDdGJ3JwZ2t9hOv/u/Ds8Gj69iWVMLgqrnqitdpMc4stL9RDen+7snVxElR1KRz+NW4gw8KUt02Nq7eHy+PPgAXBne2jtPWL9YBdV4v7vmX0UBr51vIIzN4CvgpfMFhLFpfFU5P1omMRvOUZbHWnNgHWtzOFwhJ5f70XpjfnVjYWRo6oeMZNgeryfGtshLcko8LE0ONiYWb+lLyXIMPfmUutxCxffLuYysP0WpMLAMSPJBAAAAAElFTkSuQmCC</Image> <Url type="application/x-suggestions+json" method="GET" template="https://www.google.com/complete/search?client=firefox&amp;q={searchTerms}"/> <Url type="text/html" method="GET" template="https://www.google.com/search"> <Param name="q" value="{searchTerms}"/><Param name="ie" value="utf-8"/><Param name="oe" value="utf-8"/><Param name="aq" value="t"/><Param name="rls" value="{moz:distributionID}:{moz:locale}:{moz:official}"/> <MozParam name="client" condition="defaultEngine" trueValue="firefox-a" falseValue="firefox"/> </Url> <!-- Keyword search URL is the same as the default, but with an additional parameter --> <Url type="application/x-moz-keywordsearch" method="GET" template="https://www.google.com/search"> <Param name="q" value="{searchTerms}"/><Param name="ie" value="utf-8"/><Param name="oe" value="utf-8"/><Param name="aq" value="t"/><Param name="rls" value="{moz:distributionID}:{moz:locale}:{moz:official}"/> <MozParam name="client" condition="defaultEngine" trueValue="firefox-a" falseValue="firefox"/> <Param name="channel" value="fflb"/> </Url> <!-- Context/Right-click search URL is the same as the default, but with an additional parameter --> <Url type="application/x-moz-contextsearch" method="GET" template="https://www.google.com/search"> <Param name="q" value="{searchTerms}"/><Param name="ie" value="utf-8"/><Param name="oe" value="utf-8"/><Param name="aq" value="t"/><Param name="rls" value="{moz:distributionID}:{moz:locale}:{moz:official}"/> <MozParam name="client" condition="defaultEngine" trueValue="firefox-a" falseValue="firefox"/> <Param name="channel" value="rcs"/> </Url> <SearchForm>https://www.google.com/</SearchForm> </SearchPlugin>

New NewMoon 27 Build! 32bit https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20210918-9e8144b17-xpmod.7z 32bit SSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20210918-9e8144b17-xpmod-sse.7z 32bit noSSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20210918-9e8144b17-xpmod-ia32.7z 64bit https://o.rthost.win/palemoon/palemoon-27.10.0.win64-git-20210918-9e8144b17-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1129873 - [GTK3] Implement wrapper to GtkAppChooserDialog to allow using native application chooser. r=karlt (98efe5d61) - Fixup for bug 1129873 for bustage of GTK+3 builds on elm. r=karlt. DONTBUILD. (1470214b7) - Bug 1175394 part 1 - Create an unmapped (strict) arguments object for functions with rest/destructuring/default arguments. r=jorendorff (59eebb140) - pointer style (4eefdc553) - Bug 1151149 - Throw if either the target or handler is a revoked proxy in Proxy constructor. r=efaust (c23d01862) - Bug 1158222 - Implement the new [[Set]] receiver restrictions. r=jorendorff (fc4fbc164) - Bug 1049662 - Update ES6 scripted proxies ownKeys trap to ES6 final. r=efaust (dd8eb6240) (4a7fbafa2) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1178033 - XDRBuffer: Replace isUint32Overflow by a simple check of the capacity max. r=luke (522f39612) - Bug 1191543 - Remove AutoNameVector and replace with Rooted; r=jonco (979b2fe42) - pointer style (cf34bfcf1) (45e0dadc1) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1181443 (part 3, attempt 2) - Remove nsTHashtable::EnumerateEntries(), which is no longer used. r=froydnj. (3368831d9) - Bug 1183141 - Use nsTHashtable::Iterator in ServiceWorkerManager::ClaimClients; r=catalinb (6ec0099ba) - Bug 1182966 - Part 1: Use nsTHashTable::Iterator in DomainSet::CloneSet. r=mrbkap (1c03a23d9) - Bug 1182966 - Part 2: Stop referring to the nsI class for no apparent reason in DomainPolicy. r=mrbkap (67c9e70a2) - Bug 1182977 - Use PLDHashTable::Iterator in dom/storage/. r=khuey. (accb68cb3) - Bug 1182977 (part 2) - Use PLDHashTable::Iterator in dom/storage/. r=khuey. (0dcf0792f) - Bug 1182959 (part 1) - Use nsTHashtable::Iterator in CertBlockList. r=honzab. (165e4d2d4) - Bug 1182959 (part 2) - Use nsTHashtable::Iterator in CertBlockList. r=honzab. (d24e98945) - Bug 1182959 (part 3) - Use nsTHashtable::Iterator in CertBlockList. r=honzab. (a5c240594) - Bug 1182959 (part 4) - Remove BlocklistSaveInfo. r=honzab. (2e11db520) - Bug 1182959 (part 5) - Use nsTHashtable::Iterator in nsCertOverrideService. r=honzab. (f560b8677) - Bug 1121760 (part 4) - Remove PL_DHashTableRawRemove(). r=poiru. (33267404b) - and also Bug 1182959 changes for webaudio on this tree (d15675a89) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1181452 - Add memory reporting infrastructure for Servo to SpiderMonkey. r=till. (0c503da32) - Bug 1185739 - Fix self-comparison warnings in MemoryMetrics.h. r=efaust (08da5402c) (06bd03cd6) - ported changes from mozilla: - Bug 1182969 - Use nsTHashTable::Iterator in accessible/. r=tbsaunde. (9e8144b17)

there is no any war between "evil xp users who steal code" and "honest caring Moonchild(ish) devs" there is just Tobin with his paranoia thinking everyone are against him. Palemoon has turned into a cult that attack against anyone who even raises finger against them, question anything they do or even as simple as working to improve their code and haunt them forever. And do not get me wrong. Palemoon code itself been most part very solid and in my opinion what web browser should be, not like bloat I mean firefox is. It is also last that supports java and flash that I need use sometimes to access older network equipment or other. Many say it is bad since "uses old render engine, got security vurneabilities, does not work with Netflix, or cannot be used with online im clients to voice". There is simple reasons why voice wont work and Netflix wont either, it lacks EME DRM antifeature support and webrtc which are privacy and security risk. And for security, any browser got vurneabilities and most are related to webassembly and javascript and cannot be patched so only way protect is limit allowed javascript to minium with Nmatrix or similar. Render engine is old and slow is because HTML5 and javascript that been built around google chrome for most parts. It is done on purpose to make chromium look better. It is like Internet Exploiter back in day. If web browser was what they were just program that downloads documents from online and renders them on screen like originally intended for, only slowness reason would be bad optimisation of code on browser itself. HTML stands for The HyperText Markup Language and HTTP for HyperText Transfer Protocol and that is what it purpose was originally. I am not saying there cannot be pictures or media, but Media and anything else should be handled by standardised plugins and used only if absolutely neccessary. That way anyone could do a browser themself and we would have real competition. But big companies abuses web standards and do not want competition. It is sad to see internet go way it was never meant in first place. To centralised place with only few giants. Well enough ranting from issues of internet and modern browsers If I was developer of browser or other, I would be happy if someone was able port it to platform I was unable to (I guess first need have real not artificial block of compability) and would adopt it to mainstream some point or build special version with fixes to it, not haunt developer down, but I guess I am open minded and not part of any production with word child in it. Developer behavior causes peoples not to like project no matter how good and reliable the code is, since human tends to hate things if person that they do like is involved. That causes Palemoon to loose users and eventually die away totally. Stop while you still can Moonchild(ish) and issue public apology from hostile behavior toward peoples and there is hope for project to become popular. Also if they hide source code stop recommending using of their products since "spyware concern" since without source code cannot evaluate for spyware and other issues. Word like that is going cause lot backslash to devs, escapilly on linux community. I am happy from efforts of Feodor2 and Roytam1 and anyone else who makes softwares for XP users. For long time I though was last person on earth who did not want get "latest and (not) greatest" Windows and wanted choice of OS to be thing. FF52 started suck real bad on many sites I needed use daily wanted or not, then stumbled this board and projects done here and was able to use OS I wanted better than ever before and share my knowledge with others who may need it. I may not be programmer but I got good technical knowledge.

Whatever happens from here on out, I will continue to support @roytam1 in whatever he decides to do with his browsers going forward. MCP seems hell-bent on destroying anyone and anything that tries to get in the way of their 'vision' for their browsers. The way I see it, they're on a road to self-destruction...their browsers are going to fade further into irrelevance, while people will continue to follow Roy and many others and support their hard work. MCP and their browsers are going to become more and more the reflection of everything they were once fighting against, everything they had tried so hard not to have their browsers be or to themselves become. It is a shame that they could be so arrogant not only to XP users but users of the 'regular' Pale Moon and Basilisk, so greedy about the source code, and so selfish in not allowing people to take their work and build upon it. And yet, without Mozilla they would have had nothing to build from, no starting point to begin with. They were (and are) nothing without Mozilla, much as Atlas in Teen Titans was nothing without the mechanic who did maintenance (see the episode "Only Human"). When the mechanic abandoned Atlas he was battered into spare parts...and as people abandon MCP and/or if Mozilla themselves should see fit to abandon them, they too will be battered & broken. Thank you, Roy, for all of your hard work--I appreciate you and your efforts VERY much. It ain't over 'til it's over!