Leaderboard

As if I need your "credibility" - ha! From my perspective, the BSD issue appears as just another incarnation of yourself and Moonchild whining about an "unsanctioned" build for an "unsanctioned" platform. You can't control them, so you try to intimidate them. You might be surprised the difference making a request in a reasonable manner makes versus dropping in and making demands. Machinations.. LMAO.. wow. The sad part here is that none of that was even directed at you at this point. Those links were simply directed at TechnoRelic, who has, time and again, refused to understand what was going on. And almost all of them, including the BSD one, were in the previous thread already. We've had our debates, and said our piece. Probably never going to like each other, or agree about very much. But provided you continue with this "better attitude," cease you threats, treat roytam1, his project, and its users with respect and common courtesy, then I'm mostly content to sit back and watch. I wondered how long it would take for someone to accuse me of some "past bias" against Mr. Tobin. Frankly I resent that. Sure, I don't like the guy. But everything I have said here in relation to this issue has been strictly based on the events at hand, and strictly in response to Mr. Tobin's behavior toward roytam1 and his project. I have been perfectly willing to have "civil discourse" with Mr. Tobin, provided that he cease his attacks and threats and behave like a reasonable person. If peace can be made with Mr. Tobin, that's fine too, with a couple of caveats: 1) That this "peace" not be based on giving in to threats or intimidation; and 2) That this "peace" not be based on everyone pressuring roytam1 to accept a change to his project that he clearly does not see as a priority. In fact, I had pretty much said everything that needed to be said, and even stated that I was mostly indifferent to the name changes, and stated that I would stand by roytam1 whatever HE decided. And then everyone here started jumping on the bandwagon and pressuring roytam1 to accept. Let's let roy make this decision himself, it's his project after all. He does the work. I'm interested in what HIS view is, not what is "popular." Fine, put me on that list. Not that many here seem to care what I have to say though anyway. IMO re-using Microsoft code names that are completely unrelated seems to be going off on a weird tangent. Not to mention that Microsoft has now abandoned XP and is in the process of "disappearing it" from history. As noted by others, let's have more original names, preferably with some degree of relation to (or being derived from) the parent programs... Ah, den. I thought you, of all people here, would understand where I've been coming from. If you don't at this point, I'm not sure how I could make it any clearer... And what you say is not even wholly correct. I'm not entirely opposed to the renaming. I'm opposed to it under certain conditions. The first of which is being opposed to renaming to appease people making threats. Fine, that one seems to be behind us for now. The second of which, however, you yourself contributed to by jumping on the bandwagon pushing for this. roytam1 doesn't see it as a priority, and it's his project. But now everyone but myself is pressuring him to accept this.. and for what? Like I asked before, what benefit do we gain from changing a name and a graphic? How is this "positive" pressure really any different from the "negative" pressure when roy, unlike the rest of you, doesn't see this issue as some kind of crisis? When and if roytam1 chooses, on his own, without influence from either side, to make changes to his project name or branding, I will be perfectly willing to accept it. Possibly. However, does no one but me see the intricacies of the irony in the situation? How can I phrase it... Does no one but me have a problem with the fact that roy is being pressured to allow Mr. Tobin, the very person who has been a thorn in his side for however long now, to essentially place his chosen names and his chosen graphics on roy's projects? Should roy, who has continually worked on his project and succeeded through all the criticism and nastiness, allow his ("former?") enemies to put their stamp on his work, which just recently they were trashing? Should roy, every time he builds or uses his project, have to look at a name or a graphic chosen by those who did their best to harass him and cause him any trouble they could? Should Mr. Tobin be allowed to "make his mark" (and a very visible and prominent mark) on a project he has, in the past, done his level best to destroy? I don't understand how these issues aren't striking a chord with anyone... It's not that Mr. Tobin lacks the ability. It's not that he hasn't been making a seemingly genuine and sincere effort. It's simply the sum of the situation itself. I'm not interested in "popular." I'm quite used to being in the minority, you should know this by now. Everyone here should know this, from or OS choices if nothing else. This is roy's project, not a group project. Occasionally some members are able to help, but essentially without roy this project would cease to exist. So I'm interested in what HE thinks and decides. I don't care for how everyone is "pushing" him, and you are the one who started that by pointing out roy's ignoring of Tobin's message. roy has every right to ignore Tobin if he so chooses. What has Tobin previously contributed to this project? Nothing. What had Tobin previously done to "sabotage" roy's projects? Most everything he could. So why is roy expected to "sit up and take notice" when Tobin posts? It's not as if Tobin were offering any real help with actual functionality of the project... Once again, this is not wholly correct. I am NOT trying to "derail any compromise." I have even stated that I am NOT completely opposed to changing the names. I do favor keeping them as is (say 60/40), but it's not that important. The situation is the issue. Aside from the points I've already made clarifying my standpoint I am simply disgusted with all this "bandwagonism." I may be the only one speaking now, but several others have spoken in favor of keeping the current naming convention in the previous thread. (I know, I re-read it yesterday while looking for links.) "Whenever you find that you are on the side of the majority, it is time to pause and reflect." - Mark Twain

OK that's progress; we now know the changes that broke APZ/tiled compositing came before that alpha release of FF 52. We know that SM 2.48 works, so it's pretty likely that FF 51 works too; but I haven't actually tested FF 51. Perhaps I should do that next, just to be sure.

And I will tell you, once more, that FirefoxESR (Nightly) 45.9.18 (by Roytam1) doesn't come with h264+aac decoders out-of-the-box; you have to download one yourself (instructions about Adobe Primetime CDM are to be found in a stickied thread in the XP forums, instructions/links for the LAV Filters DLLs are provided by Roytam1 himself and are to be found in a prominent location in this thread (which I've also linked to...); SIMPLE AS THAT! (Unless you consider spending 5min to install one of these "solutions" as a major inconvenience that will further deter you/anyone for that matter from using the browser(s)...) (For the record, you were also previously advised to "install" an appropriate h264 decoder by @Mathwiz, a "solution" you obviously chose to ignore... ) As for uMatrix, stick to it if it's "indispensable" to you, but don't automatically assume it's the browser's fault (and by association the maintainer's bugged coding) when you keep facing various page-rendering/media loading issues; try to post such a similar issue in the official PM forums and you'll be immediately told (and not in a courteous manner) that it's not the browser's job to adapt to a particular extension, but the other way round (BTW, "legacy" uMatrix is an abandonware, as far as I am aware - a fork is available; and WE uMatrix, if that's the one you're using with FxESR45, hasn't seen any major action for quite a long time...). FYI, Roytam1 did not create his FxESR45 fork out-of-nothing, but it's mainly based on the original 45esr code by Mozilla; this is an old codebase, and there's only limited "things" one can do to improve it (Fx45 can't be turned into Fx52+ as if by magic); Roytam1 is focusing on improving TLS support there, plus other (minor) rendering fixes are backported from another fork; all these as a courtesy to members running old hardware that lacks SSE2 instructions set support; and it's often the case that those users are simply content when a specific page justs loads in the browser, having little or no desire to start in-page HTML5 MP4 playback (which could "fry" their old CPUs or just be practically unwatchable) ... Trust me, his life would be made much easier/simpler if he stopped maintaining these forks... And please, do not post any more HTML5 MP4 video testing sites, I have myself more than a dozen to suggest; all will work fine, as long as the browser they're tested on can use patented (h264, aac) decoders and the video sites are properly allowed to load their embedded HTML5 players... I am personally done with this specific issue of Roytam1's 45.9.18 fork not playing back MP4 video in OP's machine; anyone is free to pick up the baton and pursue it further... @msfntor : Joyeux Noël !

As you all know, the motherboard of my RDD has bit the dust. So, I have replaced it with an interim one, an Asus TUV4X, which unfortunately is defective as well (extremely long boot times, most likely capacitor issues). While I am waiting for the arrival of the new one (which boots XP in normal times, just 18 seconds on an old clunky 30GB hard drive), I am in the process of setting up the OS (this time the RDD is going to be a more powerful Tualatin system in terms of processing power and RAM) and so, I have installed a genuine copy of XP Pro SP3 including an original product key I stored long ago. Well, when it came to activation, I did the good old online process, and interestingly enough, Windows activated itself without any issue... Either it was luck or I just don't know.

He wrote: ... so by "latest" it could only be firefox-45.9.18-20191207-082eb5b14-win32-sse

So you have "YourTube Box" downloader from Microsoft Store? I think you simply misunderstood ; a "YouTube Box" is just a laptop whose main/only purpose is to play back Youtube videos (displayed in a TV monitor) - at least that's how I read it here

As instructed, you need to download and place within the main app directory the LAV filter DLLs EDIT: Youtube may (and do) use non-patented decoders (VP9/VP8, opus/vorbis etc) in the WebM container, when support for patented decoders (h264, aac) is absent in the browser; however, Twitter will only use h264+aac in an MP4 container...

if your system has LAV filter installed (manually, or via K-Lite Codec Pack, etc.), my Tycho/Fx45 builds will use it automatically.

AntiVirus & Security Software: Avast Driver Updater / AVG Driver Updater ($$$, CS, ONG, UNS). (Relies on an annual subscription-based business model.) (I am not sure if you desire this but it is being listed also for the sake of completion.) Content Consumption Software: Songbird (FREE, OS). (Associated online services were discontinued in 2013.) Download from vendor Zune (FREE, CS) Download from Microsoft Misc: LightScribe System Software 1.18.27.10 (FREE, CS) Video & Photo Editing Software: Hugin (FREE, OS, ONG) Download from SourceForge VirtualDub (FREE, OS, ONG) VPN Clients: AVG Secure VPN 1.6.667 ($$$, CS) (Relies on an annual subscription-based business model.)

I didn't have to add any .dll's. I just played over a dozen YouTube videos and they all worked for me. That said, I don't quite grasp the concept of HTML5 being the end-all litmus test on whether a browser is good or not. I use my "daily" browser for 30-50 tasks throughout the year. Some tasks each and every day, other tasks monthly, others maybe only once an entire year. And viewing "videos" doesn't even break into the top 50 !!! However, I do have a "YouTube Box". A laptop with a Core 2 Duo that's over 12 years old. It's used for nothing but playing YouTube videos and sending to the big screen TV. I have the latest Arctic Fox Win32 on that laptop and it just played every YouTube video I went to. But the CPU jumped up to 35 to 40%. Granted, I prefer to use Portable Chromium version 49.0.2623.23 for YouTube playback (I mispoke in an earlier post when I cited v48). My Chromium uses slightly less CPU but the addons I run on YouTube weren't offered in Firefox variants (at least at the time I set it up). But all in all, playing videos is very VERY far down on my list of expectations for my browser. What good is a browser where the GUI takes three seconds to load but it is 100% HTML5 compared to a browser where the GUI takes one second to load but drops to 90% HTML5 ??? I'll take that one-second GUI load time every day of the week :)

In the recent past, when we were trying to come up with an interim image for both Serpent 52 & 55 @roytam1 made crystal clear he opposes identifying his builds as "for XP", since they do work OK on later NT-family OSes. This is the one thing about branding we know precisely how he feels about. +1. Yet, I do still prefer Jörmungandr to any other name for Serpent 52. By the same token, it could be RoyFox Jörmungandr, of course! https://en.wikipedia.org/wiki/Jörmungandr#/media/File:Jormungandr.jpg

I suppose I should ask how you feel about RoyFox (perhaps with variations as @Mcinwwl suggested). I know you'd rather we not rebrand at all, but if it happens, we still want your opinion on what the new branding should be. I'll give mine: I like "Moebius" for Serpent 55. I've been labeling my Serpent 55 icons "Moebius" long before @Matt A. Tobin suggested using the name. The others, I don't have particularly strong feelings about. We could use all, some, or none of his suggested names. (Although if we go with Whistler, his suggested replacement for New Moon, we do already have a rather nice logo for it.) AIUI the name New Moon is a placeholder name built into the Pale Moon source repo and is automatically given to any unofficial builds of Pale Moon; it's not something @roytam1 came up with on his own (if it were we wouldn't be having this discussion in the first place). I think there's some confusion here. All of the browsers under discussion target Windows XP and up. There aren't different browsers for different Windows versions. AFAIK none of these run on unmodified Win 2000. (With KernelEx, some may work; I don't know.) That said, I do like your idea of using a "base" name like RoyFox with a "modifier," which could be @Matt A. Tobin's suggested names. So RoyFox Whistler would be @roytam1's Pale Moon fork, RoyFox Neptune would be his Borealis fork, etc.

I actually like what Matt wants to achieve with different branding for different operating systems. But since roytam1's doesn't want to have the work of going through the whole rebranding of his browsers (icons, banners, name...), here's my take. The browser - which is actually some sort of Firefox fork - would have the same name across all OSes, a name of his own choice, I don't care which name it has (Pale Moon, New Moon, RoyFox...) BUT the version of it must have a codename that must refer to something to identify the OS version it supports. Every big company has a project with a codename (Apple with the failed Copland project and its successful macOS versions, Microsoft themselves does it since mid 90's, even I do that at my work). For example, let's be open minded a bit here, just for a exercise... what if he actually names his browser as "RoyFox", and in its about window the codename it supports is there - for example, Whistler for XP? Then you would know it is for XP. Then you would know that you need RoyFox Whistler for XP, RoyFox Neptune for Windows 2000... Same for the github repos: the branch name would be the codename, as well as the MSI/Executable installers of his browser. That's my 2 cents on this subject. Everyone wins - he can use whatever name he likes and we can have a codename in which we can identify the OS each version of his forked Firefox browser supports. End of story.

The MOZ_APP_NAME would stay the same of course, that's fine. Same with application.ini who's values failing the existence of some alt build configuration dictate the location of the application profile. SAME goes with NSIS generated installer/uninstaller and helper.exe used by both NSIS and shellservice as well as shellservice its self. Unfortunately, this is set in stone and it is too unreasonable to change that stuff now. Maybe two years ago but not now as it would cause too much end-user trouble. Not to mention it would be annoying from a patch porting point of view. So that's fine. So just need to change the name in branding configure.sh, graphical assets, and l10n. Pretty simple once you have the name and logo. Now, I can sort of dig the circles with lines in em and perhaps do something with the concept though they MAY be a bit abstract. However, I hope that modified Firefox logo is not a serious contender because clearly that would not acceptable to Mozilla as it would get the the drones all fired up in a second and of course blame us not you for it. The general problem with the New Moon branding was it was intended to be basically like the Firefox Nightly branding and while yes it pulled double duty as generic branding anyone could use, it is still intrinsically linked to us and despite the feeling from some people here that there is and never has been any confusion, I can tell you there is.. People know that Pale Moon is the older Firefox-based browser with the interface of Firefox 4-28 and that builds are sometimes called New Moon. But with the divergent path of what continues to happen to support Windows XP what is produced isn't even going to be an unbranded Pale Moon for Windows XP as most people see it. Perhaps that is how you see it but as time goes on the differences mount. Let me put it to you another way, what if we had just kept the original non-trademarked Nightly branding for Pale Moon, both Basilisk's, and you also created your other half-dozen Firefox-based builds.. ALL called Nightly because that is what was there. How could you tell them apart then? Is it reasonable to put the burden on us to explain to people that the Windows XP builds you produce aren't the same as someone else producing Windows 7 unbranded builds or unbranded mac builds which also use the New Moon branding because mac isn't at the official level yet. The un-knowledgeable user who doesn't read more than maybe two sentences of a paragraph would assume New Moon == Pale Moon because they look the same and because despite being referred to as generic branding the name is too unique and intrinsically linked with us. This is the result of a decision made six years ago and it turns out to not have been a very good one on our part. Let me also say again, that this happens in the wild. THERE IS CONFUSION because I have specifically gone out of my way to berate and s*** on the confused user because it p***ed me the hell off and does every single time. Should I? No. Do I? Yeah. Should I continue to do so.. Well despite what one may conclude I actually don't know.. I do know that I don't really want to be angry about it anymore. I do know that over the past two years it has accomplished nothing. I also know that roytam1 took the unofficial branding as-is but hasn't been bothered to change it for whatever reason that may be. I do know I am a half-way decent designer and have the technical knowledge to implement it easily for roytam1 to slot into place. I also figured I had nothing to loose by str8 up offering to do it instead of expecting someone else to. A very common situation I find my self in a lot these days actually. I talked, bitched, complained, pleaded with and begged SeaMonkey for almost 10 years to not turn out the way it turned out and it accomplished nothing but in the Pale Moon project and beyond to the Unified XUL Platform, lots of things have gotten done through hard a** work via cooperation, coordination, and discussion and maybe that should be applied elsewhere. Especially to places that have historically annoyed the hell out of me for whatever real or imagined reason. After all, it is a process to better ones self and help make world at large better too. Can't have it all in a day but you can't have anything if you don't try. So I am trying (and yes there is likely a joke in there). Besides, I can't keep calling the paradigm "new" if it is the same old crap, eh?

If you delve back into the original 200-page thread, you'll find plenty of suggestions for new names. None caught on, probably because we soon had far too many to choose from! I tried to avoid that this time, figuring @Matt A. Tobin's suggested names were good enough and I didn't want to start another avalanche of name suggestions So far the leading alternative suggestion seems to be RoyFox and variations thereon. Which would also be fine by me. ================ Well yes, but I think the immediate concern is rebranding New Moon, Serpent, Navigator, and Interlink (mail/news). The others (FF 45 SSE, Arctic Fox, K-Meleon) can remain as they are for now. So maybe four polls (five if you consider Serpent 52 and 55 separate).

... Actually, king in French is roi (Le Roi = The King, La Reine = The Queen); but obviously this is going OT at the speed of light, so I had better shut up... https://en.wikipedia.org/wiki/Roy

Anyone who finds the suggested "Whistler" branding for NM 28 objectionable, should let us know now, while there's still time to change it. Seems pretty innocuous to me, but you never know what might turn folks off unless you ask! For the @roytam1 NM browsers that are usually updated each week, the best way to do what you want would be to wait until the version number changes, then download the last build of the previous version. That would be closest to the eventual release version. OTOH, if you always want the latest, greatest version, @i430VX has an installer that takes the drudgery out of updating your browser! I'm sure it doesn't mean the same thing in Chinese, but in Latin, "Roy" means "king;" so for me, "RoyFox" conjures up an image of a fox with a crown on its head! Then again, that might trigger a "raccoon"-like reaction with some folks.... Edited to add that @caliber suggested a nice "RoyFox" logo a few pages back. No crown but it looks nice to me.

I think I'd just stated the possibilities, not giving out "Yes" or "No". I'm open my mind for having rebranding, or not, by how people want. As I stated before, whatever rebranding happen or not I'll still build binaries for my use. remember my first PM public build is 2017-09-29 (hey, I kept building PM builds over 2 years! in the past, I built my own firefox 3/4 builds from 2010-04-15 to 2012-04-27, and also firefox 1.x to 2.x builds starting from 2006-03-16)

I'm sorry LoneCrusader but by invoking the bsd-wip github issue you have lost any credibility among any of us over here. I will take responsibility for what I said on the Pale Moon forums and in my channel. I even take responsibility for what I said in that github issue BUT in THAT CASE I was in the right and there is no denying that from any rational mind. Could a word order change have not evoked such a disproportionate response from them? I have asked that question many times since then. I want to say yes but I know those bsd people are batshit insane. They don't respect intellectual property OR software licenses wanting to treat everything as public domain and/or theirs without cause and are at a level of fanaticism that outshines even my self. So no. You don't get to cite that as a valid argument against me to promote blatant anti-Tobinism. I won't stand for it. You're done. Fortunately for the rest of everyone who isn't you, I am not going to let that impact the start of what I hope will be better times. So to everyone else, nothing has been impacted by LoneCrusader's machinations. I stand by what I have offered and suggested.

new ArcticFox win32 test build is uploaded: http://o.rths.ml/gpc/files1.rt/arcticfox-27.9.19.win32-20191221.7z - Bug 1134518 - Add test to ensure we don't lose shistory entries when switching a browser's remoteness r=Mossop (f7bd1b4e2) - Bug 1134518 - Use the globalMM for ContentTask's frame script to prevent it from being loaded twice into a docShell swapped to another browser window r=bustage (da4f3899c) - Bug 883609 - Porting tests to new Session Restore backup mechanism;r=ttaubert (f53b11a6f) - Bug 1134518 - Add xpcshell test for shistory caps on clean shutdown and fix existing tests r=Yoric (3ed696a4c) - Bug 1077738: Retain whether history entries are set to persist in session history and restore that. r=smacleod (a0be00dc4) - update (2959bddc8) - Merge pull request #19 from wicknix/master-good (cda043440) - Merge pull request #20 from rmottola/master (ed9f72c2e) - fix duplicated IsWin10OrLater() function (02510748c) - add missing bit of Bug 1134280 - Get rid of Tag() - patch 1 - Is{HTML,XUL,MathML,SVG}Element and IsAnyOf{HTML,XUL,MathML,SVG}Elements, r=smaug (4b86381cc) - Bug 960959 - Use RunState to keep track of the SessionFile's closed status r=yoric (a4cb3aaa3) - remove telemetry initialization part, not needed anyway: removes warning (dd0ef756d) - Bug 1134518 - Send a state object instead of a string to SessionWorker.write() r=Yoric (bd5b96e4d) - Bug 1157235 - Remove unused sessionstore-state-write notification r=Yoric (884843b11) - Bug 1150529 - Remove code for expired telemetry histograms r=Yoric (b86b58e55) - add specific stuff that could hurt mac (156375c79) - clean (904cbaa94) - Bug 1073502 - Restore closed windows even when there are no open windows on startup r=yoric (2c12eea64) - Bug 940777 - Simplify about:blank handling in session restore (r=ttaubert) (5298de7ed) - Bug 1135498 - Get rid of the unused browser.__SS_restore_data property r=smacleod (a87fabb3f) - Bug 923315 - Ensure that sessionstore.js writes don't interfere with browser_upgrade_backup.js r=yoric (31c6a52c0) - Bug 883609 - Porting tests to new Session Restore backup mechanism;r=ttaubert (7c04c1156) - Bug 1107941 - Removing old upgrade backups if too many exist. Max upgrade backups is defined in preferences. Tested with mochi tests. r=Yoric (857fa2844) - Bug 1134518 - Cap shistory entries in the SessionWorker when shutting down r=Yoric (f0a9f43ac) - Bug 1100223 - Make calling loadURI() on pending tabs work as expected by marking the tab as no longer pending and simply waiting for the restoration to finish r=billm (5f4f766b7) - Bug 1152341 - Failure to read one of the session file candidates shouldn't stop us from trying further r=Yoric (ff1bccd2f) - Bug 1034075 - Add more details to SessionFile AsyncShutdown blocker. r=ttaubert (fc0aace02) - Bug 1031298 - Add a histogram for counting unrecoverable sessions. r=yoric (95b377fef) - more stuff to do (044d0dbff) - revert default of showQuitWarning because it exposes a bug which corrupts the profile or session storage (714e4eb78) - Bug 1056443 - Use correct URL in location bar when switching processes (r=ttaubert) (7e6a54793) - Bug 1109875 - When unloading a frameLoader flush all pending state changes by sending a final update message r=billm (4264bb7d1) - Bug 1161928 - Move epoch handling from ContentRestore.jsm to content-sessionStore.js r=billm (9bc20bf8a) - Bug 1145942 - Use the frame message manager to revive crashed tabs upon navigation r=billm (a2ee3704d) - Bug 1161928 - Require an epoch (managed in the parent) included in every message sent by the frame script to get rid of TabState.flush() calls in restoreTab() r=billm (11a126155) - Bug 1169892 - Avoid extra round-trip when a pending tab is reloaded r=billm (569786f54) - Bug 1125411 - OSX: turn CoreLocation provider on, r=cpeterson Also, expose this setting in about:config (fe7fb5620) - Bug 1136956 - Set CoreLocation provider to non-release only in firefox.js. - r=cpeterson (7e971cf02) - update (110be9f3f) - Merge remote-tracking branch 'upstream/devel' into fix-winbuild (11f9fe3b2)

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rths.ml/boc-uxp/mailnews.win32-20191221-beb2221f-uxp-d6baead6c-xpmod.7z Browser-only Suite Win32 https://o.rths.ml/boc-uxp/bnavigator.win32-20191221-beb2221f-uxp-d6baead6c-xpmod.7z source patch (excluding UXP): https://o.rths.ml/boc-uxp/boc-uxp-src-xpmod-20191123.7z Official repo changes since my last build: - Update gitignore so that Pale Moon and Basilisk will not be tracked if they are symlinked/junction'd into the tree (855250ff) - Update commit pointer (beb2221f) For UXP changes please see above.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.ml/basilisk/basilisk52-g4.5.win32-git-20191221-fd382bb-uxp-d6baead6c-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.5.win64-git-20191221-fd382bb-uxp-d6baead6c-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rths.ml/basilisk/basilisk52-g4.5.win32-git-20191221-fd382bb-uxp-d6baead6c-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rths.ml/palemoon/palemoon-28.9.0a1.win32-git-20191221-806d807dc-uxp-d6baead6c-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.9.0a1.win64-git-20191221-806d807dc-uxp-d6baead6c-xpmod.7z Official UXP changes since my last build: - Remove Pale Moon from the Unified XUL Platform repository (4e34c5746) - Remove Pale Moon 7zstub (094e74ff6) - Update metadata in UXP 7z-stub installer (e6a3515a1) - Update 7z-stub README to reflect the current state of its use. (e7d4713e0) - Remove Basilisk from the Unified XUL Platform repository (06494f307) - Issue #1323 - Move XULRunner back to topsrcdir (e2de507e0) - Bug 1317376 - Part 1: Remove unreachable code and remnants from the self-hosted implementation. (e23b013ad) - Bug 1317376 - Part 2: Detect Promise self-resolution when resolving through the Promise resolving fast path. (f589ef816) - Bug 336705 - Part 1: Support creating and resolving Promises without resolve/reject functions. (cb732e5fd) - Bug 1336705 - Part 2: Add self-hosting intrinsics for resolving/rejecting Promises and adding reactions. (1fd726c6b) - Bug 1343481 - Part 1: Remove {JSFunction,JSScript,LazyScript}.isGenerator() method. (9163aaebb) - Bug 1343481 - Part 2: Stop using StarGegerator for async function. (f07d5707c) - Bug 1343481 - Part 3: Add JSOP_AWAIT and rename {yieldIndex,yieldOffset} to {yieldAndAwaitIndex,yieldAndAwaitOffset}. (3a3de55aa) - Bug 1343481 - Part 4: Add Add GeneratorObject.{isAfterYield,isAfterAwait}. (73c873200) - Bug 1343481 - Part 5: Rename AsyncFunction-related names in Promise.cpp to explicitly say Async Function. (4f88fc851) - Bug 1343481 - Part 6: Add native functions wrapper for GetInternalError and GetTypeError. (cba3f6142) - Bug 1343481 - Part 7: Add BytecodeEmitter::emitDotGenerator and make yield/await nodes unary. (79b5eb14b) - Bug 1316098 - Optimize out result object allocation for await/return in async function. (d0d9a4f43) - Bug 1344753 - Update for-of stack depth in ControlFlowGenerator::processWhileOrForInLoop. (f5fa6cfea) - Bug 1317389: Change property attributes for generator and async functions to match ES2015/2017. (f87b1b885) - Bug 1331092 - Part 0: Define NOMINMAX to avoid compile error from min/max macro on windows. (5e1f00240) - Bug 1331092 - Part 1: Add Symbol.asyncIterator. (82f9efff9) - Bug 1331092 - Part 2: Implement Async Generator except yield*. (d5086ac3a) - Bug 1331092 - Part 2: Implement Async Generator except yield*. (8e2f6a759) - Bug 1331092 - Part 6: Support JSOP_TOASYNCGEN in JIT. (bbd1fef78) - Bug 1331092 - Part 7: Implement Async Generator yield*. (ef44324d9) - Bug 1331092 - Part 8: Support JSOP_TOASYNCITER in JIT. (580dfb2af) - Bug 1331092 - Part 9: Implement for-await-of. (5bdfdb678) - Bug 1331092 - Part 11: Await on the innerResult.value when innerResult.done is true in yield*. (55728c964) - Bug 1355399 - Switch property retrieval in Async-from-Sync Iterator prototype methods. (63eee6325) - Bug 1364608 - Stash rval in AsyncIteratorClose. (dd1cbde15) - Bug 1379525 - Part 1: Await on the value before yielding or returning inside async generator. (38c1d558a) - Bug 1379525 - Part 2: Properly handle rejection in async-from-sync iteration. (4a5ed79c6) - Bug 1390082 - Implement AsyncGeneratorQueue with simpler array operations. (e0eee318c) - Bug 1352312 - Enable Async Iteration. (c9bddfca7) - Bug 1454285 - Part 1: Specify the current scope when emitting await and .generator. (c66d25512) - Bug 1454285 - Part 2: Disallow using innermostEmitterScope while the value does not match the bytecode environment. (6c3e42ac6) - Merge pull request #1327 from g4jc/async_iteration (07d0bcbf1) - No Issue - Fix indentation and account for system libevent in ipc/chromium/moz.build (a3e93d08d) - Issue #1328 - Part 1: Change default monospace font to Consolas for all localizations where this would be set to Courier New. (342f94295) - Issue #1328 - Part 2: Change tests that require Courier New explicitly. (0f67e7b22) - Issue #1328 - Part 3: Add fuzz to reftests and fix misc other tests. (eea149e73) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (11ce27f0d) - Issue #1328 - Follow-up: Increase font size for changed monospace fonts. (8220776c9) - Issue #1322 - Part 1: Remove the DOM Promise guts. (fb96b43b5) - Issue #1322 - Part 2: Remove --enable-sm-promise buildconfig switch. (cdea310f1) - Issue #1322 - Part 3: Remove DOM promise interface gunk (d46126240) - Issue #1322 - Part 4: Fix WebIDL.py parser for line endings and wrong IDL name (c7ae364a8) - Merge pull request #1330 from MoonchildProductions/DOM-promise-removal (3332f584c) - Issue #1316 - Reduce compiler warnings in ICU (368170bdc) - Enable layers acceleration by default on GTK platforms. (ce250e9cc) - Issue #1219 - Align computed DOM styles with mainstream behvior. (d6baead6c) Official Pale-Moon changes since my last build: - Remove Platform Code (846fcb459) - Move browser/ to palemoon/ (93c20bef5) - Overlay Pale Moon 28 (1f08c8017) - Version bump (Start Pale Moon 29) (509cbf622) - Add Comm Build System (75dd33577) - Add platform submodule (e573bfa52) - Add a mach stub (20ea829d0) - Update commit pointer (1afb8b2ec) - Re-create README.md (8c1e4fb00) - Add 7zstub (b2577a078) - Merge branch 'master' of https://github.com/MoonchildProductions/Pale-Moon (d8661ecb1) - Make Pale Moon build in a comm configuration (07a6051d2) - Issue #1697 - Add executable bit to scripts. (980687b89) - Merge pull request #1698 from trav90/buildsystem-work (9e6597608) - Issue #1697 - Correct a couple of paths for Mac build (9d6b4534e) - Merge pull request #1699 from adeshkp/mac-build-split-platform (af8643918) - Update gitignore to account for someone being clever with ntfs junctions or other filesystem links (af431d801) - Update platform commit pointer (806d807dc) Official Basilisk changes since my last build: - Add git stuff (db902e7) - Add Comm Build System (3d5a69a) - Update readme (5a343e9) - Add executable bit to scripts (744b3b2) - Add platform submodule (0e3a8df) - Update readme (c2eb348) - Update readme ONE MORE TIME (ab111e9) - Update gitignore to account for someone being clever with ntfs junctions or other filesystem links (67f840a) - Make Basilisk build in a comm configuration (fd382bb) My changes since my last build: - The front-end(PM/BK/etc.)/back-end(UXP Goanna engine) separation works is not happened in my repo for the time being, but for tracking their changes I put my portions over their repo in my working copy. If the rebranding really happens here, front-end/back-end separation works will happen here and there may be an unified front-end repo for my front-end works.