Leaderboard

It's at value of 4. With Nvidia panel the setting value is also 5 or 4. My monitor was very bright at its default values of brightness 50 and contrast 50, too. I have a 24 inch Fujitsu Siemens from 2006. (It a has a Philips panel inside). All German assembly. The current refresh rate I use is 60HZ. Soon to be two decades old, runs like a clock, I may recap it later (change capacitors). It's hard to buy German made caps nowadays.

FYI, mentioning members works with Chrome 60 (released 2017-07-25) as the minimum version. Chrome 59 is the version where you can't reply there on MSFN at all.

Dave, you're absolutely right! 60Hz is definitely the right frequency for such flat screens of that era, even if they can do 75, it usually leads to reduced quality.

ClearType is easily switched off in Vista, so you will see identical fonts as if you were on XP, this is not the case with Windows 7, the fonts will still be blurry no matter what you do. Windows 7 renders everything blurry and bluish, mp4 videos, any film you watch on windows 7 looks awful. I don't know about Win10, I guess your driver there is different?

The aboutbuttuon is a special custom button coded quite unusually. It is generated in JavaScript by the var variable and is a menu button. When hovering on all buttons, you will notice that this button renders differenly from all the others. I think the code imported by the stylesheet buttons_on_navbar_button_roundness.css can't target this kind of custom button. It is simply not recognised as a standard toolbar button by the stylesheet. To change the appearance of this button in a toolbar (e.g. nav-bar) itself, you have to change the code inside the aboutbutton.uc.js file directly. Cheers, AstroSkipper

@dmiranda The solution to let the custom button aboutbutton recognise by the CSS stylesheet buttons_on_navbar_button_roundness.css is a bit more complicated than I thought. You have indeed to change the code of the script aboutbutton.uc.js. It seems to be a class issue. This is the first part of the original script code from line 1 to 26: (function() { if (location != 'chrome://browser/content/browser.xul') return; try { CustomizableUI.createWidget({ id: 'about-toolbarbutton', type: 'custom', defaultArea: CustomizableUI.AREA_NAVBAR, onBuild: function(aDocument) { var toolbaritem = aDocument.createElementNS('http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul', 'toolbarbutton'); var attrs = { id: 'about-toolbarbutton', class: 'chromeclass-toolbar-additional', type: 'menu', removable: true, label: 'about Seiten öffnen', tooltiptext: 'about Seiten öffnen' }; for (var a in attrs) toolbaritem.setAttribute(a, attrs[a]); return toolbaritem; } }); } catch(e) { }; I changed the class of this button in line 15 from 'chromeclass-toolbar-additional' to 'toolbarbutton-1 chromeclass-toolbar-additional': (function() { if (location != 'chrome://browser/content/browser.xul') return; try { CustomizableUI.createWidget({ id: 'about-toolbarbutton', type: 'custom', defaultArea: CustomizableUI.AREA_NAVBAR, onBuild: function(aDocument) { var toolbaritem = aDocument.createElementNS('http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul', 'toolbarbutton'); var attrs = { id: 'about-toolbarbutton', class: 'toolbarbutton-1 chromeclass-toolbar-additional', type: 'menu', removable: true, label: 'about Seiten öffnen', tooltiptext: 'about Seiten öffnen' }; for (var a in attrs) toolbaritem.setAttribute(a, attrs[a]); return toolbaritem; } }); } catch(e) { }; This change seems to be enough to let the CSS stylesheet buttons_on_navbar_button_roundness.css recognise the custom button aboutbuttuon as a standard toolbar button. Thus, the button can be rounded by this CSS stylesheet. Here is a screenshot to show the result of my change (I added borders around the buttons via CSS code for better visibility ): The positive side effect of this modification is that the custom button aboutbuttuon behaves as a normal toolbar button from now on, even if it is not rounded off by such a CSS stylesheet. Cheers, AstroSkipper

sc qc wscsvc If you run Command Prompt as administrator, type in and run the above command, what does it say? The command queries the service's configuration.

My monitor brightness is at 4, yes, at 4, contrast at 18. Nvidia panel is at 5 brightness and 2 contrast.

Really. really bad fonts, I'm very sorry you have this problem. Are you sure it runs at 1280x1024 Pixel, 32-bit colour? Because those usually run at 1280x1024 Pixel and 60hz, not at 75hz. At 75hz it would be like 1024x768.

What is the resolution of your monitor?

Firefox and MyPal catch d3d9.dll file but there is a conflict with hardware acceleration if it is enabled

I told you many times about 1030 being superior. What can I say, we all learn something, I guess, I spent several years before I found the right driver for me, But hey, no one stops you from those topics getting deleted.

I use 13.5.1030, and the fonts look very good, maybe 13.5.2044 isn't for your system after all. The fonts look like here. The settings I use is in the image I already sent (here). Sorry, can't send BMP - the limit is up.

anti-aliasing gamma korrektur = aus

Never heard of those, AstroSkipper thank you for letting us know!

Yes, I know about browser not being 3D, still nVidia driver seems to apply these settings and render it as if it was a 3D app. It even suggests to choose those options for each of my browsers individually.

You're not the only one who is not satisfied with chromium/windows7 fonts, look here. ""So the year is 2023 and MS Edge still seems to be the only Chromium-based browser that follows Windows settings for font-rendering..."" https://msfn.org/board/topic/185877-changing-sk_gamma_contrast-without-recompiling-chromium/

That confirms what I've been saying about different levels of brightness/contrast in different versions.

Go to Manage 3D settings, it's there for me.

NCH Debut Sceen/Webcam Cature works okay too.

That's why I wrote that you don't need any VGA files from Win7.

Yes, It's new for me too. I have downloaded it and installed on offline Windows XP x64 machine. I have not found silent install switch. Installation was fast and in English. UI doesn't looks bad. I will post some screenshots later. Good is it run on XP, hopefully they not spying a lot.. Someone needs to check if there are any hidden connections.

Thanks for the information! I personally have never heard of it before. I found a review on MalwareTips Forums which is from 2022 and unfortunately not positive. The author does not recommend this security programme. Here is a link: https://malwaretips.com/threads/huorong-internet-security-2022.119308/ But one review is of course not the world.

Screenshots won't do it real justice due the compression, about win7, yes, no way to tweak it to display normal fonts, Vista can be tweaked though.

What about iOS?

This is how the fonts look like on my old Siemens XP laptop with a very low screen resolution 1366x768 (it can't go more). Driver nVidia 346.26. Take a note, the website automatically switches me to the Dutch website https://www.dpd.com/nl/nl/ because I am from Holland.

For XP and this browser I use suggested by @D.DrakernVidia icafe 347.26. The fonts look marvellous!

Every video driver renders fonts differently. I'd start with searching the right one for you. It's a long path of trial and error.

No such flag in M115.

I remember minibrowser crashing when inserting USB drives (it is not the same thing but it relates to external media stuff), user @realisty found out that by turning off the "Enable new USB backend" flag in "chrome://flags/" made the browser not to crash anymore. I don't know if that can help (I also don't know if that flag still exists on 115).

You're very welcome! It would an interesting topic since my experience with Windows 7 was nothing but annoyances and grievances.

After a long while, I successfully "installed" CustomCSSforFx (https://github.com/Aris-t2/CustomCSSforFx). This was covered in passing by @AstroSkipper, but I was lost implementing it (as many reading this thread, I reckon). Below a short how-to summary. First, download and follow the instructions in the first post (https://www.mediafire.com/file/m84enyyuz7up01y/Mypal_68_CB_requirements.7z/file). This will set up the basics. MAKE SURE TO RENAME userChrome.css to my_userChrome.css. Second, download and paste the latest version of CustomCSSforFx into the Chrome folder in yout Mypal profile. All of it: you can later on delete the css files and images you don't need, once you played with the different settings, as described below. Third, open userChrome.css and userContent.css in your preferred text editor. In those files, play around commenting and uncommenting the @import "./css/WHATEVERYOUWANTTOTRY, by adding or deleting /* at the beginning of each @import. You'll have to run mypal after every change(s) you make. For instance, in userContent.css I uncomment @import "./css/aboutaddons/recentupdates_category_always_visible.css"; /**/ and @import "./css/aboutaddons/availableupdates_category_always_visible.css"; /**/ (to comment out add /* before each @import you don't want to use; to uncomment, delete said /*). Idem in userChrome.css. For instance, I uncomment @import "./css/tabs/tabs_below_main_content.css"; /**/ and comment out all the others I don't want to use, yet. In userContent.css, change and uncomment the last line @import "./my_userContent.css"; /**/ to @import "./my_userChrome.css"; /**/ (see first step). This will load @AstroSkipper's custom buttons, such as the one below. That's it.

The stylesheets are not intended to be installed completely. You choose what you want to change and what you like. I only use a very few of them. Custom CSS stylesheets must be permanently adapted to new Firefox versions. Stylesheets that worked in a previous version do not necessarily have to work in the subsequent version. Mypal 68 is based on Firefox 68.12.0esr from August 2020. The regular Firefox 68 version (not esr) was released in July 2019. Thus, you have to look mainly for custom CSS stylesheets published from July 2019 to August 2020. Search for tabs_below_navigation_toolbar_fx68.css which depends on tabs_below_navigation_toolbar_fx65.css which in turn depends on tabs_below_navigation_toolbar.css! That means you have to copy all three files into your profile subfolder chrome\CSS and import the tabs_below_navigation_toolbar_fx68.css file only in your userChrome.css file via the following command: @import "./css/tabs_below_navigation_toolbar_fx68.css"; The good is that once you found working stylesheets they will work in Mypal 68 probably forever. Is mostly finished. It is not for public as I have not changed the name from Firefox to Mypal. Replace the string Firefox by the string Mypal in all files using the "replace all"-function of an editor as, for example, Notepad++! This is very easy and can be done in minutes. In any case, your compatriots would surely appreciate a working German language pack for Mypal 68.13.x. Cheers, AstroSkipper

Here are two screenshots to show where and by what means modifications have been done to the user interface of Mypal 68.13.5b: The colours of the areas mean how the modification was made. Red stands for CSS only, blue for JavaScript only, and green for both, JavaScript + CSS. Cheers, AstroSkipper

I have tested Malware Hunter in version 1.173.0.791 on my system, and it is still compatible with Windows XP. Accordingly, I updated my article. Cheers, AstroSkipper

On my Windows XP Professional SP3 32-bit partitions, I have installed all .NET Framework versions from 1.1 to 4.0 with all hotfixes and updates.

@tekkaman This thread is exclusively about security programmes for Windows XP . Therefore, your observation or problem is unfortunately off-topic. You should post it in the Windows 7 forum. BTW, I had no problem to install Panda Antivirus Free in the version 22.00.01 under Windows XP. And the installer didn't want me to install .NET Framework 4 either, presumably because my Windows XP was and is fully updated. Cheers, AstroSkipper

Here is a review of Panda Free Antivirus from November 2022, so still quite up-to-date, but in any case better than any experiences from 2015: https://www.lifewire.com/panda-free-antivirus-review-1356582 Cheers, AstroSkipper

I totally forgot to mention I already wrote an article about Panda Free Antivirus. Here is my article: Cheers, AstroSkipper

Subject: Panda Free Antivirus Some months ago, I had carried out my own tests with the result that Panda Free Antivirus detected and deleted my test malware. In a real Windows system, not in a VM. So, I can confirm that Panda Free Antivirus is fully working. It is one of the rare antimalware ptogrammes which are still up-to-date and still receive programme updates under Windows XP. However, we all know the real security problem is very often in front of the computer. In such cases, a good programme like Panda Free Antivirus can't help anymore, either. Cheers, AstroSkipper

Welcome to MSFN and my thread! Thank you very much for your nice compliment! I will continue when I have more time available. Researching, checking, and writing is very time-consuming, unfortunately. Greetings from Germany to Belgium, AstroSkipper

New regular/weekly KM-Goanna release: https://o.rths.ml/kmeleon/KM76.2-Goanna-20200201.7z Changelog: Out-of-tree changes: * update Goanna3 to git 3c4a44c16..6a75a56f2: - import changes from `devel' branch of rmottola/Arctic-Fox: - Bug 943820 - Add visibleLabel attribute/property and tests. r=ttaubert (95540e489) - Bug 902729 - Add a new telemetry probe for session lifetimes. r=ttaubert (725e51e1a) - Bug 1150529 - Remove code for expired telemetry histograms r=Yoric (6a1540c7f) - Bug 732303 - Redesign safe mode dialog with the profile reset option. r=dolske, ui-r=limi (8a0253b18) - Bug 894188 - "resetSupported is not defined" in safe mode dialog. r=jaws (a45930696) - Bug 498181 - Offer to reset a user's profile if it was last used more than two months ago. r=jaws (5295b1629) - fix duplicted entries (eb068619a) - Bug 1063702 - Update all Reset Firefox strings and relevant UI to new UX requirements. r=MattN (4771a9da5) - remove some DEVTOOLS and console related code, not found in FF/TFF (11b163829) - Bug 1147236 - Use AppConstants in session store code (r=ttaubert) (68b6ceedf) - fix redeclaration of cc (b1b1611b0) - bug 1137792 - Ignore the first timing for an add-on r=mossop (59e48d895) - Bug 1140113 - Catch direct (and some indirect) callers of CreateDrawTarget* and deal with failure. r=mstange (89cf1d361) - Bug 1010552 - Breakpoints not removed from server when tab is closed;r=jlong (bf63d0b31) - Bug 1139181 - Add missing MIRTypes to StringFromMIRType(). r=efaust (d716f2fe9) - Bug 950373 part.2 Don't consume keys which are used by <tree> for navigation in session restore UI r=enndeakin (06435f06b) - Bug 925771 - Generate consecutive window IDs to avoid collisions. r=ttaubert (74c81ef33) - Bug 931891 - [Australis] Backed out bug 887515 and the followups (bug 896291, 909662, 896896). r=ttaubert (b8f02497e) - Bug 930901 - Move TabState and TabAttributes to their own JSMs r=billm (be255adac) (3fd1b0d56) - Reverted all AF front-end changes to restore session restore function. (5abf6194f) - import changes from rmottola/Arctic-Fox: - Bug 1137166: Change the Content moreStrict sandbox pref to an integer to indicate the level of sandboxing. r=tabraldes (b5333092c) - Bug 1140806 - Initialize JS random seed using arc4random on Android and BSDs. r=fitzgen (c39ad68da) - Bug 935862 p1 - add flag for ex/ch unit usage. r=heycam (47b3a36a3) - Bug 935862 p2 - add various userfont lookup methods. r=heycam (ede140ecc) - Bug 935862 p3 - implement selective reflow for downloadable fonts. r=heycam (9d6abc4aa) - Bug 935862 p4 - add reftests to sanity check @font-face reflow behavior. r=heycam (8c56a5f2f) - Bug 935862 p5 - handle SVGTextFrame reflow correctly. r=jdaggett (b5f420748) - Bug 935862 p6 - fixup problematic reftests. r=heycam (13fd7b36b) - Bug 1140946 - tweak fall-through for ex/ch restyle on font load. r=dbaron (e05284f0a) (00c9e7452) - update UXP version of NSS 3.48.1, and import changes from tenfourfox: - #369: add back build system changes [partly] (a7ee0d3a4) - #369: bustage fix for opt builds (cc2e336b2) (80ce3707b) - import changes from tenfourfox: - #587: update TLDs, certs, pins, etc. (35584e5e6) (a85a1fd22) - port changes from tenfourfox: - #584: M1507180 M1598605 (7b58ac561) - fix M1607443 as a precaution (b8657e696) - #587: M1513855 M1596668 M1602944 M1599420 M1595399 (35a4358b3) (a61b8c3d3) - import changes from rmottola/Arctic-Fox: - Bug 1130891 part 1 - Add W3C HTML5 ruby tags to atom list. r=smaug (ea17ccc67) - Bug 1130891 part 2 - Add option in document encoder for including ruby annotation in plain text. r=roc (d3e0dff72) - Bug 1130891 part 3 - Add param to HTMLCopy to allow copy with ruby annotation. r=smaug (8e75e87a7) - Bug 1130891 part 4 - Do copy with ruby when the whole selection is inside ruby. r=smaug (891d7590d) - Bug 1140741 - Teach JitProfilingFrameIterator to read DebugModeOSRInfo. (r=djvj) (f468e332e) (603e20b30) - import changes from rmottola/Arctic-Fox: - Bug 932865 - Add ThreadHangStats for collecting background hang telemetry; r=vladan (2f08a076b) - Bug 932865 - Add way for telemetry to iterate over active threads; r=froydnj (535615d3d) - Bug 1128768: Part 3 - Update BHR to allow for hang annotations; r=vladan (0b880a667) - Bug 935092 - Add ThreadStackHelper to get a thread's pesudo-stack; r=BenWa (1422cfe4d) - Bug 942488 - Don't report pseudo-stacks without SPS profiler. r=nchen (e160a7a08) - Bug 946817 - Don't assert mPseudoStack on B2G. r=BenWa (9f846df3b) - Bug 951431 - Don't get stacks during profiler runs on Linux; r=BenWa (15036e907) - Bug 978262 - Ignore duplicate frames when getting BHR stack. r=froydnj (964721b1b) - Bug 985155 - Add signal trampoline on ARM Linux to work around kernel bug. r=snorp (cb8a7846c) - Bug 995730 - Convert xpcom/threads/ to Gecko style. r=froydnj (fe150404e) - Bug 1013326 - Distinguish chrome and content scripts in pseudostack; r=snorp (81273c977) - Bug 1023461 - Remove temporary stack buffer in ThreadStackHelper; r=snorp (cf5a717c2) - Bug 1023461 - Record filename and line number for chrome JS entries; r=snorp (10c89808f) - Bug 1022456 - Fix modelines in xpcom/{base,glue,io,string,threads}/. (48dbc0416) - Bug 1016441 - Switch to using real-time signal in ThreadStackHelper; (2c5f818be) - Bug 1016629 - b. Use RAII class to assign mStackToFill; r=snorp (769eae130) - Bug 1016629 - c. Add define for ThreadStackHelper pseudostack support; r=snorp (67def0d2f) - Bug 1016629 - d. Add and implement GetNativeStack method in ThreadStackHelper; r=snorp r=jseward (46c52f2be) - Bug 1016629 - e. Implement platform-specific code for filling in context; r=snorp r=jseward (e6a66858b) - Bug 1016629 - g. Avoid ASan flag when copying stack; r=snorp (0159628b5) - Bug 1045176 - Unbreak build on non-SPS platforms after bug 1016629. (f1d60d838) - Bug 1047123 - ThreadStackHelper should use UniquePtr<uint8_t[]>, not ScopedDeleteArray. r=jchen (0e4af313c) - Bug 1049161 - Fix ThreadStackHelper thread handle permissions on Windows; r=snorp (c05172b1c) - Bug 1050185 - Make ThreadStackHelper::FillThreadContext Valgrind-friendly. r=nchen (368725774) - Bug 1050440 - Remove repeated js::RunScript frames in ThreadStackHelper (2a79600b3) - Bug 1046841 - Fix more style violations in previously touched .cpp files in xpcom/. r=froydnj (02afe2493) - Bug 1069694 - Remove or move around functions in OldDebugAPI. r=shu (177197302) - Bug 1069694 - Remove OldDebugAPI from the browser. r=shu (b8c917d42) - Bug 1100911 - For MacOS builds running on Valgrind, make ThreadStackHelper::GetStack be a no-op. r=nchen. (d99c02e16) - Bug 1091758 - Report full paths for most chrome scripts; r=snorp (2b72e7878) - Bug 1109291 - Include better paths for hanging chrome scripts in profile extensions directory; r=snorp r=bsmedberg (1997b9532) - Bug 1113416 - Don't read stack labels inside hang monitor sighandler; r=nfroyd r=snorp (9688f6069) - bug 1146027 - more final r=froydnj (7b0f295e5) - Bug 1164090 - Check for Windows path separator in BHR file name; r=snorp (f014b4d78) - Bug 1169034 - include <cstdlib> in ThreadStackHelper.cpp to declare correct overload for std::abs; r=jseward (874d4447e) - Bug 1182996 - Fix and add missing namespace comments. rs=ehsan (054fc00b2) - Bug 932865 - Collect thread hang stats in BackgroundHangMonitor; (ac80c8e9f) - minor anticipated fixes to get it compiling (2bd701d15) (8f529f64f) - import changes from rmottola/Arctic-Fox: - Bug 1115438: Move PluginModuleParent's invocation of CreateToolhelp32Snapshot off the main thread; r=jimm (e2c4f828f) - Bug 1141093: Ensure that FinishInjectorInitTask::PostToMainThread is no longer executing before leaving FinishInjectorInitTask::Run; r=dmajor (7ca55b82d) - Bug 1140725 - Fix unreachable code after semicolon-less return statement in nsContextMenu.js. r=jst,dolske (bbb360053) - Bug 486172 - Don't ignore a -p command line argument when using the Xremote protocol. r=bsmedberg (8492d3df8) - Bug 1128798 - [e10s] Make a version of nsIContentPolicy that doesn't pass the node as a parameter (r=mrbkap,tanvi,ckerschb) (bbd6147ee) (6a75a56f2) * 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

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rths.ml/boc-uxp/mailnews.win32-20200201-2376eb06-uxp-64c8c65cf-xpmod.7z Browser-only Suite Win32 https://o.rths.ml/boc-uxp/bnavigator.win32-20200201-2376eb06-uxp-64c8c65cf-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: - Restore basic CLOBBER detection in the comm build system (2eb8519f) - Complete the clobber file detection (6a096e55) - Update commit pointer (e22fca9c) - Update commit pointer (9de0bab0) - Rewrite mach stub to be less crap (62a19e8f) - Fix typo in mach stub (105f0fb4) - Fix windows detection in mach stub (655ebc2f) - Update commit pointer (e9cc9d08) - Fix mach short sha for platform (2376eb06) 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-20200201-2d98a15-uxp-64c8c65cf-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.5.win64-git-20200201-2d98a15-uxp-64c8c65cf-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-20200201-2d98a15-uxp-64c8c65cf-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-20200201-c9294d3d3-uxp-64c8c65cf-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.9.0a1.win64-git-20200201-c9294d3d3-uxp-64c8c65cf-xpmod.7z Official UXP changes since my last build: - Issue #1356 - Remove -moz-user-input disabled to improve event handling. (42e481677) - Issue #1356 - Restore older syntax. (1f8d50825) - Issue #1349 - Stop 2xx FTP responses from causing browser to hang. (8bb5db350) - Fix whitespace. (7d53919c2) - Merge pull request #1371 from athenian200/ftp-list (a1cce3b2b) - Issue #1360 - Part 1: Simplify layers acceleration prefs. (282b791ac) - Issue #1360 - Part 2: Update tests for changed preferences. (90773547e) - Bug 1276438 part 1. Move the implementation of the .body getter from nsHTMLDocument to nsIDocument. (a2b56b295) - Bug 1276438 part 2. Move the implementation of the .body setter from nsHTMLDocument to nsIDocument. (32f3f8826) - Bug 1276438 part 3. Align the .body setter with the spec a bit better. (ce285b6f2) - Bug 1271549 - Remove details and summary preference. (bc8543bf7) - Bug 1274159 - Part 1: Support looking up definitions by using constructor as a key; (2d31ebf6b) - Bug 1274159 - Part 2-1: Include the name of relevant interface in nsHTMLTagList.h; (244277a3f) - Bug 1274159 - Part 2-2: Support HTMLConstructor WebIDL extended attribute for custom elements; (5222f6e9d) - Bug 1274159 - Part 3-1: Add HTMLConstructor to HTMLElement and its subclass; (6ea0acf75) - Bug 1274159 - Part 3-2: Update web-platform-test expected result; (5b814fffd) - Bug 1274159 - Part 4: Add test cases for HTMLConstructor; (bac01e30f) - Bug 1309184 - Implement upgrade reaction for custom element reactions. (3a97503b3) - Bug 1341693 - Don't need to check GetDocShell() when creating CustomElementRegistry; (5cf46e2f8) - Bug 1347446 - Move custom element reactions stack to DocGroup. (25a33c712) - Bug 1351979 - Change CustomElementRegistry::Define code to properly propagate out JS exceptions; (16cd53bd8) - Bug 1350960 - Release CustomElementReactionsStack in TabGroup thread when DocGroup is going away. (ba8fb9dc5) - Bug 1309147 - Part 1: Implement the support for CEReactions in WebIDL parser. (08d22f03e) - Bug 1309147 - Part 2: Add the name of 'this' value's JSObject* for codegen to generate CEReaction code. (20799ce18) - Bug 1309147 - Part 3: Implement the support for CEReactions in Codegen. (df23f78ad) - Bug 1309147 - Part 4: Add CEReactions for CustomElementRegistry. (e05574703) - Bug 1309147 - Part 5: Eliminate performance cliff when accessing CEReactions code. (d8109fa9a) - Bug 1341898 - Make nsDocument::IsWebComponentsEnabled use a cached bool pref; (859fbc139) - Bug 1357002 - Part 1: Cache dom.webcomponents.customelements.enabled preference; (9abc9b2b7) - Bug 1357002 - Part 2: Don't call SetupCustomElement() if the custom element feature is pref-ed off; (88925e150) - Bug 1359346 - Implement custom element state; (e86aac28b) - Creating customized built-in elements without relevant definitions registered first shouldn't throw NotFoundError; (9d51b9d06) - Bug 1325279 - Put the reaction queue in CustomElementData structure instead of using a map; (a2c7b5f1d) - Bug 1347634 - GetCustomElementData and SetCustomElementData don't need to be virtual; (59c26110c) - Bug 1377993 - Make node slots less memory hungry in common cases. (cc533eaee) - Bug 1340027 - Part 1: Add DOM CEReactions annotation. (1674f8f75) - Bug 1340027 - Part 2: Add HTML CEReactions annotation. (3fd2f6194) - Bug 1340027 - Part 3: Add CSSStyleDeclaration CEReactions annotation. (db86d423e) - Bug 1340027 - Part 4: Add DOM parsing CEReactions annotation. (7a1cb5040) - Bug 1340027 - Part 5: Add XSLTProcessor CEReactions annotation. (4c9eab4d2) - Bug 1315885 - Part 1: Add ShadowRoot CEReactions annotation. (19f08038f) - Bug 1315885 - Part 2: Avoid rethrowing exception in CustomElementCallback::Call. (6ff1c0c52) - Bug 1315885 - Part 3: Transfer the ownership of ReactionQueue's entry due to re-enter CustomElementReactionsStack::InvokeReactions. (e6733c927) - Bug 1315885 - Part 4: Implement callback reaction for custom element reactions. (53c9b77ed) - Bug 1299363 - Part 1: Implement construction stack. (32f1ff0f8) - Bug 1299363 - Part 2: Allow prototype swizzling in html constructor. (3d44a0b7f) - Bug 1299363 - Part 3: Remove unused argument in UpgradeCandidates. (ca596f282) - Bug 1299363 - Part 4: Hold a pointer of ElementQueue in ReactionsStack instead. (d7e5ad445) - Bug 1353647 - Fix the custom elements v0 upgrade inconsistency; (515c46e69) - Bug 1299363 - Part 5-1: Make the constructor created by document.registerElement() also works with construction stack. (bbb717ec1) - Bug 1299363 - Part 5-2: Implement new upgrade steps. (704318ea0) - Bug 1334051 - Part 1: Include namespace in attributeChangedCallback. (08fc05747) - Bug 1334051 - Part 2: Invoke attributeChangedCallback only if attribute name is in the observed attribute list. (bf004bb63) - Bug 1332233 - prevent resource leak in CustomElementRegistry::Define. (49f597e7f) - Bug 1398401 - Add preference check for custom element setup. (45a4aaf7e) - Bug 1301024 - Part 1: Set CreateElement/CreateElementNS is attribute. (5840b63cc) - Bug 1301024 - Part 2: Implement create an element steps. (f50503df9) - Bug 1392970 - Part 1: Make CustomElementDefinition ref-counted and put it in CustomElementData. (8573c572f) - Bug 1392970 - Part 2: Get CustomElementDefinition from CustomElementData when possible. (42331663e) - Bug 1334043 - Part 1: Replace attached callback (v0) with connected callback (v1). (186782301) - Bug 1334043 - Part 2: Make nsContentUtils::EnqueueLifecycleCallback static. (3d4c41009) - Bug 1334043 - Part 3: Update tests for connected callback. (01dfbc928) - Bug 1334044: Replace detached callback (v0) with disconnected callback (v1). (6bbb9f062) - Bug 1121994 - Implement adopted callback for custom elements. (8e6ce5fae) - Bug 1319342 - Clone a node should enqueue an upgrade reaction. (6ec385fbd) - Bug 1406297 - Fix Document.createElement must report an exception. (4dda3f603) - Bug 1407937 - Move mDefinition from CustomElementReacion to CustomElementUpgradeReaction; (2cbd6d369) - Bug 1352290 - Add assertion to CustomElementReactionsStack::Enqueue to ensure upgrade reactions aren't scheduled to BackupQueue; (1aa6cdcc1) - Bug 1352082 - Avoid shifting a signed integer left in C++. (5b862aa38) - Bug 1352082 - Avoid shifting a signed integer left in C++. (72a6fd4d2) - Bug 1355493 - Tweak bufToHash() and reduce the number of pre-interned elements. (56925e1f4) - Bug 1355493 - Tweak bufToHash() and reduce the number of pre-interned elements. (4503b51a4) - Bug 1355493 - Tweak bufToHash() and reduce the number of pre-interned elements. (738190dfd) - Bug 1355769 - Avoid malloc for nsHtml5ElementName when processing a non-interned element name. (e387308d9) - Bug 1355769 - Avoid malloc for nsHtml5ElementName when processing a non-interned element name. (016a21c41) - Bug 1355769 - Avoid malloc for nsHtml5ElementName when processing a non-interned element name. (f7bb7e81e) - Bug 1355479 - Remove isindex on the Java side and allow the C++ side to reduce malloc in attribute handling. (90d19b0a3) - Bug 1355479 - Flatten attribute storage in the HTML parser to AutoTArray to avoid malloc. (650f6b5eb) - Bug 1355479 - Flatten attribute storage in the HTML parser to AutoTArray to avoid malloc. (e5557d43d) - Bug 1358037 - Inline the methods of nsHtml5ElementName and nsHtml5AttributeName. (41e477e2c) - Bug 1358037 - Inline the methods of nsHtml5ElementName and nsHtml5AttributeName. (5d4200f56) - Bug 1358037 - Inline the methods of nsHtml5ElementName and nsHtml5AttributeName. (76a4af340) - Bug 1366241 - Change memory layout of element name and attribute name hashes from sorted to level order BST in order to take advantage of cache during lookup. (e17a17766) - Bug 1366241 - Change memory layout of element name and attribute name hashes from sorted to level order BST in order to take advantage of cache during lookup. (a8511d983) - Bug 1366241 - Change memory layout of element name and attribute name hashes in HTML parser from sorted to level order BST in order to take advantage of cache during lookup. (fce396323) - Bug 1410790 - Add more assertion in CustomElementData::SetCustomElementDefinition and GetCustomElementDefinition; (b7f890e02) - Bug 1378079 - Add attribute 'is' to HTML parser. (4c193edca) - Bug 1378079 - Part 1: Gecko changes for adding attribute 'is' to parser. (004b231d0) - Bug 1378079 - Part 2: Introduce throw-on-dynamic-markup-insertion counter. (0b6548613) - Bug 1355779 - Skip interned nsHtml5ElementName lookup for Custom Elements (ones with hyphen). (1ef7d1752) - Bug 1355779 - Skip interned ElementName lookup for Custom Elements (ones with hyphen). (bec4d0ecd) - Bug 483155 - Put Gecko content creator function pointers on ElementName. (9bf83c6a7) - Bug 483155 - Put content creator function pointers onto nsHtml5ElementName. (d163c367d) - Add missing elements from Bug 483155 (97ed13a9f) - Add missing space to ElementName.java self-regeneration code. (0f9746b6e) - Fix ISINDEX (ea3562536) - Fix aAttributes (950275abe) - Fix Build: We don't have SVG or MathML prefs yet (e2fc7a9d4) - Regenerate Parser for 483155 (dd6749f7d) - Bug 1378079 - Part 3: Complete the steps related to custom elements in "create an element for a token". (a0014ac6e) - Bug 1406325 - Part 1: Make sure custom element state is custom before sending callback. (e62385604) - Bug 1406325 - Part 2: Set CustomElementData when cloning a node. (c199dd22e) - Bug 1406325 - Part 3: Refactor custom elements clone a node. (72d4c0b8d) - Bug 1406325 - Part 4: Use mType for LookupCustomElementDefinition and also removing parts of v0. (fb657f7a1) - Bug 1406325 - Part 5: Implement try to upgrade. (93313b0ce) - Bug 1405335 - Remove custom element attached and detached callbacks validation checks (7e9efb0f2) - Bug 1400762 - Make dom.webcomponents.enabled pref doesn't control CustomElements feature (37d09da24) - Bug 1396620 - Part 1: Remove created callback for custom elements (f576d8f0f) - Bug 1396620 - Part 2: Fix compartment mismatch crash when doing old prototype swizzling for custom element (4083a9abf) - Bug 1415761 - Catch the exception and rethrow it after invoking custom elements reactions; (8db81508a) - Bug 1419643 - Don't need to lookup custom element definition for a non-custom element (14d115cfe) - Bug 1405821 - Move microtask handling to CycleCollectedJSContext (43a811307) - Bug 1406922 - Make CycleCollectedJSContext to handle microtasks and make MutationObserver to use them (2077cdb41) - Bug 1419305 - Part 1: Use MicroTask on CustomElements correctly (0405d843b) - Bug 1419305 - Part 2: Keep processing remaining elements in ElementQueue even if some of elements are already unlinked (a8bf089e8) - Bug 1407669 - Fix custom element creation hides uncatchable exceptions from the constructor. (53319e5df) - Bug 1413815 - Convert 'observedAttributes' to a sequence<DOMString> (e8f95f974) - Bug 1421544 - Lazy push/pop CustomElementReactionsStack entry; (d84323905) - Bug 1430034 - Fix attributeChangedCallback isn't fired with correct newValue when the attribute value is an empty string; (0cea94242) - Bug 1430951 - Avoid element name atomizing to improve performance of LookupCustomElementDefinition (3c70b297c) - Merge pull request #1374 from g4jc/custom_elementsv1 (22ed46f7c) - Force CLOBBER (d56573bb9) - Merge branch '1360' (71416f9b7) - Update platform version. (54fbb5c75) - Issue #1360 - Enable acceleration by default on all known-good platforms. (c4b0715ba) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP into form-disabled-issue (3c4f414db) - Issue #1356 - Add tests. (7a697172f) - Merge pull request #1357 from athenian200/form-disabled-issue (ed88b9984) - [WebRequest] Remove AddonManagerPermissions leftovers (e57998f68) - Issue #1355 - Speed up the traversal of a table row frame's child cells (fd26b8453) - Issue #1342 - Remove support for system ICU (00a5321c9) - Issue #1342 - Remove support for system NSPR/NSS (499b28739) - Merge pull request #1376 from win7-7/optimization-1-pr (64c8c65cf) Official Basilisk changes since my last build: - Issue #4 - Update appstrings.properties changing hardcoded Firefox to Basilisk (1911122) - Issue #3 - Update NSIS Publisher string (e690015) - Issue #2 - Enable WASM and its Baseline JIT in application preferences (73e1335) - Revert "Issue #2 - Enable WASM and its Baseline JIT in application preferences" (82ada3a) - Issue #2 - Enable WASM and its Baseline JIT in application preferences (b419211) - Restore basic CLOBBER detection in the comm build system (c653391) - Complete the clobber file detection (2d98a15) Official Pale-Moon changes since my last build: - Issue #1702 - Restore basic CLOBBER detection in the comm build system (02d8514cd) - Issue #1702 - Complete the clobber file detection (cf40511d1) - Change sessionstore cache behavior to soft refresh (693c62876) - Update comment (fcdeaee4a) - Issue MoonchildProductions/UXP#1360 - Pale Moon front-end changes (e97b588d4) - Issue MoonchildProductions/UXP#1360 - Add omitted XUL preference entry (00e358e20) - Issue MoonchildProductions/UXP#65 - Remove AppConstants Pale Moon.. again. (8a67d2608) - Bump platform commit and unstable version. (202f3c916) - Issue MoonchildProductions/UXP#1360 - Fix a dumb mistake. (7bbdbce85) - Update platform commit pointer (4decbed5a) - Merge pull request #1712 from MoonchildProductions/UXP-1360 (c9294d3d3) My changes since my last build: - Revert "[WebRequest] Remove AddonManagerPermissions leftovers" (2b2df633f) - Reverted leftovers from commit "ported mozilla upstream change: Bug 1355441 - Reuse StackNode in TreeBuilder to avoid malloc. r=hsivonen." (d39d2b841)