Leaderboard

My only suggestion - do not "live for the like". If you seek something to research today, do a Google/Bing/DuckDuckGo/Swisscows search for "self worth tied to like button", rephrase it different ways, let the results lead you to other searches. Then after reading at least 30 articles, both pro and con to the "like button", then ask yourself if you should be worried about mina or legacyfan "liking" posts or not. Live well, my friend.

My initial load time with default agent above is cca. 30 seconds. The one I suggested drops it to cca. 13 seconds. It's been known for a long time YouTube's UI (aka. Polymer) is slow, especially in browsers not implementing Web Components and such.

I will not continue with this project, I have outgrown it. Thank you for all your kind comments, advice, etc. My modified versions are removed - they are unsafe due to sandbox bypass, embeded videos do not work.

I jumped from Firefox 96.0.3 to 110 today, got about 6 extra points on Speedometer. I mostly use Pale Moon, but a bit of speedup is refreshing, though it also costs more memory and I lose some extensions (though also gain some other extensions - web altering ones really, not browser altering ones). Also needs more RAM, Pale Moon needs cca. 400 MB for 1x MSFN tab, 1x Speedometer tab, 2x GitHub project page tabs, Firefox needs 700 MB. 32-bit versions.

Firefox forks ? security researchers found out back in 2020 some unexpected telemetry connections during start up on the original Firefox Quantum toward Mozilla servers. I can't recall if they were using WireShark or a more sophisticaded tool. like this https://www.reddit.com/r/PrivacyGuides/comments/z6rq1f/this_study_says_firefox_leaks_a_lot_of_info_and/

@yoltboy01 This thread should be retitled “Future of Chromium on Windows 7.” (The future of Chrome on “vanilla” Windows 7 is simply version 109.)

I know it's already been (sort of) answered, but let me add: (a) The UXP engine underlying MailNews changes just about every week, so every time UXP is updated, it's possible to build a new version of MailNews. TBH, most changes don't really affect MailNews (e.g., email doesn't use JavaScript, so JavaScript enhancements don't improve MailNews), which is, I assume, why BOC hasn't updated in a while. This week's build contains a change that does affect MailNews: an enhancement allowing OAuth2 to be used with email addresses that are actually GMail "in disguise." (I used to have such an email address.) (b) There might be other differences, but the only one I've noticed so far is that IceDove lacks OAuth2 as an authentication option; I'm guessing because OAuth2 was added to UXP after Hyperbola stopped IceDove development. So the OAuth2 code is "in" UXP but can't be accessed from IceDove. (c) The former: IceApe is Hyperbola's reworking of SeaMonkey on UXP, further reworked by @roytam1 for compatibility with older Windows versions, and to include the latest UXP enhancements.

uBlock Origin (Web Extension) v1.47.3.1 (shown here) is actually: "uBlock0-1.47.3b1-git-20230224-gbb203d9" There's an XPI for that in the GitHub repo: https://github.com/gorhill/uBlock/releases/download/1.47.3b1/uBlock0_1.47.3b1.firefox.signed.xpi If one downloads the XPI on disk and then tries to install it in Mypal68, (I assume) it won't, because it requires Fx 79+, so I have no clue how it got there in the first place... Sometimes GitHub misbehaves and when you left-click the XPI link directly on the GitHub releases page, it'll bypass the "gecko" version check... Another hypothesis: Although functionally incompatible with a gecko68 engine, build "uBlock0-1.47.1b0-git-20230215-ge83dbd8" (while available as an XPI) would have no issues installing; perhaps that one progressively auto-updated through to 1.47.3b1 somehow? gorhill only changed the gecko version to 79, as far as auto-update was concerned, on Feb 19/20th ...

If you're using XP SP2, then I am afraid that BSODs are expected to happen.

- CSSE - Common Sense Security Essentials (self explanatory) Don't open random attachments, check the integrity of the websites you're getting executables from, check digital signatures, and so forth. Show file extensions in Windows Explorer. Ear on the side of caution with p2p. Use a good content blocker in browser, like uBlock Origin. Don't relive the IE6 glory days and mash every big green download button you cross paths with. - VirusTotal Really awesome for scanning executables and installer files. - COMODO Cleaning Essentials Pretty decent portable AV scanner. Runs as far back as Win2k with extended kernel, gets frequent database updates all without needing new clients. Has a Killswitch tool as well, which is just a big process list - Unchecky Not an AV tool per-se. It just unchecks most ad offers in junk ridden installers, in case you miss the tic boxes yourself. Can help prevent PUPs for the untrained eye. - Malwarebytes 3.5 Older client, still gets database updates. 1.x clients worked until recent. See pertinent thread: https://forums.malwarebytes.com/topic/191650-malwarebytes-3-frequently-asked-questions/#comment-1243649

I can't front--I ended up going back to 7 x64. It's really the '20 versions rule' that keeps me on 7, because at this point in time I'm not in a situation that really necessitates moving up to 10. I'm using Chromium 90 right now, well below the cutoff point (109) for pre-10 users. The idea is to take it version by version, staying 20 behind the newest, then when we get to the 130/110 milestone, I'll probably move up to Firefox (whatever is most recent, stay 20 versions behind that and keep moving up until/unless we hit a dead end; at that point I'll probably review the options that are available by then). I have a feeling 7 will probably be usable much as XP was for a long time to come, maybe to the end of the decade and some change. My PC is old enough that it can run 7 and 10 with full driver support, so I'm taking advantage of that to stick with the older, faster 7. But I have no problem moving up to 10 in the future--if you've got at least a dual core and add Classic Shell (and make sure to turn off all the optional crap during the install process), it's actually not too bad.

On Internet, you're not alive, only the posts are visible, not you.

Your experience may differ, though. But it's good that you are open to trying all different builds of Windows 10 to experiment. I really liked Windows 10 beginning 1903, because of the light/dark mode (though, I still prefer the old mode Windows 10 version 1809 (and older) had, which is: dark Windows mode, and light apps mode, and it's possible to keep it like that in 1903 and later, thankfully), and the feature to change the cursor size and color.

why is liking someone based on liking posts?

That is a very good point. The Chromium developers are on the right track in terms of optimizing for speed (and I really hope it stays that way), but it is inevitable that as the capabilities of the browser increase, so too does the CPU/RAM required to make it run well. Chromium 109, I am sure, would run as well or better than 96, but it would come at the cost of a slightly higher CPU/RAM footprint. Actually, I just went back to Chromium 90 as I noticed some 'quirks' with 96 (including certain files not downloading with a left click; I would have to copy/paste the link into the address bar--I have had this happen in Chromium 109 too, ungoogled and Hibbiki builds, so I'm sure it's not a hardware or OS issue). It's inevitable that I'll have to move up to 96 according to the 20 version rule, but I want it to happen over time, gradually. In real world use 90 seems to be offering equal if not better performance compared to 96 and 109, and is a bit more stable in my experiences (I've had 96 freeze and lock up several times with a certain number of tabs loaded, if the memory use is high enough; this does not seem to affect 90). Obviously, I'm not making sales pitches to convince people to use an old version of their favorite browser; everyone has their own use cases and unique needs. But as someone who uses a PC that is now over a decade old, there is a lot to be said for staying on old versions of software, unless you have a use case that absolutely necessitates making the switch to something more up-to-date. No doubt I'm speaking to the choir here, since the people who frequent this site know their stuff better than the 'average' person.

Me not liking your posts doesn't mean that I have issues liking posts. If I had issues liking posts, I would've told you that, don't worry.

AFAIAA, all people who posted about BSODs on the issues of GitHub, were using Mypal 68 in multiprocess mode. I think this is the main reason for a BSOD in Mypal 68. Maybe, it will work in the final release of Mypal 68 whenever it comes.

What can he say? Has he ever used or tested my system? No. Therefore, he can't say anything regarding my system, unfortunately. And BTW, if you want to post interesting facts about Mypal 68 here in terms of extensions or custom buttons, or maybe about the new nightly build, you are welcome here at any time. But any comparisons with other browsers are off-topic, unfortunately.

No, but I use Mypal 68 in single-process mode. In multiprocess mode, your chance to get a BSOD is much better.

Of course, my dear ArcticFoxie, I couldn't care less about those likes, I just wanted an answer from the one who boasts that he CAN make those likes, that's ALL. Thank you very much!

I agree with you as I also like installers better but for web browsers I don't care much any more. I for one have had several issues with the original Firefox which was unable to start because of some registry problems hence I prefer the portable editions now.

I'm a little worried because I don't see any likes from you Mina on my posts lately? Not even from legacyfan?... So nice posts and no reactions, strange, must be a thief who gets all these likes... or my posts don't attract you anymore all of a sudden... or it's the MSFN's fault...

Said it before, will say it again - never allow javascript by default! This alone will prevent 99.9999999% of "security vulnerabilities". No, I don't know the "exact" percentage, but 9 nine's has to be pretty close!

re: cookie steeling This is one of the biggest reasons I have never understood why people want to "save" tabs and even logins from one browsing session to the next. And even complain that a browser isn't "portable" if their logins can't be carried between different computers. There are people here at MSFN that would "complain" that they can't close 360Chrome with a HUNDRED PLUS tabs open and wonder why their next "session-restore" would be SLOW because they WANT their next launch to open those HUNDRED PLUS tabs !!! Never made one lick of sense to me! I clear all cookies, tabs, cache, et cetera with every exit! And I never log into any bank account without that being the ONLY thing I do during that browsing session.

x64 is decent, with my Renesas USB controller. The only things hooked up to my onboard USB is my keyboard and mouse. Also interested in running 2000

I hope you are well @XPerceniol, sending vibes of wishing you well.

New NewMoon 27 Build! 32bit https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20230225-4e6138a54f-xpmod.7z 32bit SSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20230225-4e6138a54f-xpmod-sse.7z 32bit noSSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20230225-4e6138a54f-xpmod-ia32.7z 64bit https://o.rthost.win/palemoon/palemoon-27.10.0.win64-git-20230225-4e6138a54f-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 966986 - Part 1: Fix format of DataTransfer.getData(text/x-moz-url) and return each text and URL as a separated item on Mac. r=smichaud, vlad (4de2b9ee3f) - Bug 966986 - Part 2: Return true from nsDragService::IsDataFlavorSupported for text/x-moz-url-desc and text/x-moz-url-data on Mac. r=smichaud, vlad (210fb284cc) - Bug 1167834 - Fix -Wwritable-strings warnings in widget/cocoa/. r=smichaud (933fa44bb4) - Bug 1206766 - Show meaningful module offsets in stack traces even when no symbol found. r=spohl (406e2019dc) - Bug 1205399 - Remove some leftover Growl strings. r=mstange (44dd51e2cd) - Bug 1205399 - OS X: Implement disabling Notifications for the site from the native notifications. r=mstange (4c5c3c3c41) - Bug 1208685 - Dedupe alert.css and cleanup alert.js heading. r=bgrins (669f2f5347) - Bug 1208295 - Show an additional action on OS X notifications to open notification settings. r=mstange (4562ca98f5) - Bug 935434 - Make XUL alertNotifcations use dir/bidi parameter by setting the according css direction attribute. Set lang attribute for labels. r=jaws (0e1e045f28) - Bug 1202933, Part 1 - Show the origin for XUL notifications. r=MattN,wchen (836ca78e53) - Bug 1202933, Part 2 - Show the origin for OS X notifications. r=MattN,wchen (468b702443) - Bug 1201397 - New layout of XUL Notifications. r=MattN (1133670c5d) - Bug 1209602 - XUL: Implement disabling notifications for a site. r=MattN (980f441952) - Bug 1218315 - Replace NS_LITERAL_STRING(...).get() with MOZ_UTF16(...) on widget. r=nfroyd (4605f28ee6) - Bug 1221449: Add null ptr check and fix variable shadowing in OSXNotificationCenter.mm. r=spohl (6064ea34ec) - Bug 1052776 - fix role=alert usage and ensure alert events fire, r=MattN (45cb398d87) - Bug 1217621 - Show settings action for XUL notifications. r=jaws (9cb70137c2) - Bug 1205172 - Do Not Disturb Button for Push Notifications on Windows. r=MattN (16b068c676) - Bug 1219458 - Remove the notification animation until we have better transparency support. r=MattN (bcd89030e2) - Bug 1214029 - Use double-quotes for strings in alert.js. r=MattN (a8b2a60ab6) - Bug 1213421 - Truncate long body and title text in notifications. r=MattN (b91c55cb1b) - Bug 1213421 - Follow-up, set the bodyText even when text is not being truncated. r=MattN (47212a10ca) - Bug 1216161 - XUL notifications on Linux can't be closed. r=MattN (0ad4abe149) - Bug 1218781 - Padding on the right side of notifications is missing when an icon is supplied. r=MattN (b0661b491c) - Bug 1218785 - Remove top and bottom margins on images in notifications. r=MattN (fb5f74249c) - Bug 1218780 - Notifications shouldn't use a hand cursor. r=MattN (be6da71ee0) - Bug 1218789 - Close button and gear button are misaligned in notifications. r=MattN (a6d684f008) - fix misspatch (e9a9840e80) - Bug 1148933 - Remove old storageservice.js and tests. r=gps (6308b7230f) - reorder (2095058419) - Don't mix GPU adapters across processes. (bug 1183910 part 10, r=jmuizelaar) (fa313da63d) - Don't attempt to use WARP after D3D11CreateDevice crashes. (bug 1201202, r=bas) (10d8424a75) - Bug 1207437 (part 1) - Don't recompute Windows feature levels. r=dvander. (0b0d3c11a1) - Bug 1207437 (part 2) - Don't re-get D3D11CreateDevice. r=dvander. It's always obtained during gfxWindowPlatform initialization and put into sD3D11CreateDeviceFn. (db99647c33) - Bug 1207437 (part 3) - Fix and disallow warnings in gfx/thebes/. r=dvander. (4cf28c971d) - Bug 1207437 - Extra qualification fixup. (05ab331aaa) - Search for a matching DXGI adapter in content processes. (bug 1225283 part 2, r=jrmuizel) (c1f715dd91) - Add IPC helpers to marshal DXGI_ADAPTER_DESC. (bug 1225283 part 1, r=mattwoodrow) (932804aab6) - Bug 1208465 - Part 1: Fix some reftest annotations. r=jrmuizel (725601b236) - Bug 1208465 - Part 2: Disable using Direct2D when 1.1 is unavailable. r=jrmuizel (2ad1fc80bd) - Bug 1196335 - Disambiguate the strings for scoped gfx reporter and D2D1.1. r=dvander (0cb2c1534c) - Bug 1222569 - fix -Wformat warning in gfxWindowsPlatform.cpp; r=Bas (95f339a567) - Bug 1195844: When checking for old DisplayLink versions, look for a few other DLLs. r=jrmuizel (8a316e876f) - Bug 1197296. Check for errors more during bug testing. r=Bas (21405bfe27) - Don't assume D3D11CreateDevice() gives back non-null devices. (bug 1209268, r=milan) (7208b1e52d) - Bug 1222569 - fix initialization order in gfxWindowsPlatform.cpp; r=Bas (530f2510b7) - Don't use Direct 2D 1.0 if Direct3D11 is using WARP. (bug 1207665 part 2, r=jmuizelaar) (a6f6aef92a) - Bug 1207258 - Give back the ability to run direct write without D2D, but only with a *force* preference. r=dvander (283454081b) - Bug 1097321 - Fix DoesD3D11TextureSharingWorkInternal to handle Intel/AMD configurations. r=Bas (efa1d2eeef) - Bug 1223002 - Always call ReleaseGrFace to balance GetGrFace, even if the face is null. r=jdaggett (06cb8447ba) - Bug 1225125: If all drawing is just clipped out anyway, just push a regular group, blending mode won't matter. r=jrmuizel (78a90991d4) - Bug 1223440 - Implement NativePanZoomController::setIsLongpressEnabled so long-press detection can be disabled during testing. r=kats (b8e31ab26a) - Bug 1202050 - Use UntransformTo in a few more places in APZ code. r=botond (6c43dda3c3) - Bug 1228501 patch 1 - Remove decorations parameter to nsFont constructors. r=jdaggett (ea43ab6167) - Bug 1228501 patch 2 - Remove nsFont::decorations member variable. r=jdaggett (57f9cc2520) - Bug 1228501 patch 3 - Remove nsFont::BaseEquals. r=jdaggett BaseEquals and Equals were made the same by patch 2, so BaseEquals can be removed. (925a469540) - Bug 576927 - Use saturating multiply when calculating zoomed app units to avoid integer overflow. r=roc (ab0caaa9c7) - Bug 1228501 patch 4 - Remove nsStyleFont::CalcFontDifference, which now duplicates the list of tests in nsFont::Equals. r=jdaggett (46523eaf4c) - Bug 1228501 patch 5 - Remove NS_FONT_DECORATION_* constants. r=jdaggett Decorations in Gecko are associated with the CSS 'text-decoration' property, so the constants should live in nsStyleConsts.h, as they largely already do (since the names defined there are the vast majority of the uses). (2895dfb610) (e4c23c8471) - import changes from `dev' branch of rmottola/Arctic-Fox: - remove PM alertTime custom (911dd825ec) - Bug 1208346 - Alert service Do Not Disturb backend. r=jaws (0047051b4e) - Bug 1208346 - Fix manualDoNotDisturb build bustage on Android. r=bustage (39275a49bd) - Add some shadow warnings back (64eb2adf55) - some window fixes by Roy (72e6a9b98e) - remove parameter of DoesD3D11DeviceWork (243dfb24f4) - Bug 1197296. Check the error code of Map. r=bas (9debd274fd) - Bug 1221348 - Part 1: Unify crash signatures. r=jrmuizel (80763d326d) - Bug 1221348 - Part 2: Fix texture sharing detection code on Intel. r=jrmuizel (fb0390850d) - Bug 1097321 - Add layers.amd-switchable-gfx.enabled pref. r=jrmuizel (3963a35cbc) - Bug 720589 - mMatchCounts may be accessed with a nonexisting index. r=neil (fdbdd7e228) - Bug 1224975 - add telemetry for font loading. r=m_kato (013a6e8fc7) - Bug 1188376: Split Hello Telemetry values from general WebRTC r=jib (3887cc3201) - Bug 1198883 - Part 1: Improve ICE candidates telemetry probes. r=bwc (2d02a3d752) - Bug 1198883 - Part 2: Added WebRTC ICE candidates to Telemetry. r+vladan (fa8032043f) - Bug 1201926 - Add support for keyed histograms to Fennec's Telemetry module, r=nalexander (8b96ebf026) - Bug 1213780 - Fix Telemetry reporting repeated hang annotations for Chrome hangs. r=aklotz (afde812b08) - Bug 1128768: Part 4 - Update telemetry to serialize BHR hang annotations; r=gfritzsche (7c1b8f5fa5) - Bug 1215540 - Fix Telemetry reporting repeated hang annotations for Thread hangs. r=aklotz (afed35f06f) - Bug 896740 - Limit the number of chrome-hangs reported to Telemetry. r=vladan (a37ba72225) - missing bits of Bug 932865 - Expose thread hang stats (c19c41ae06) - Bug 1187138 (part 1) - Replace nsBaseHashtable::Enumerate() calls in toolkit/ with iterators. r=froydnj. (ba92a8464f) - Bug 1121040 - Don't send RETURN keypresses to content while a satchel autocomplete entry is selected. r=Gijs,smaug (762efd7cc8) - Bug 1145146 - Remove offensive comment from nsFormFillController r=mak (7a6b0eb4e1) - Bug 1136085 - Part 1 - Don't store & collect subsession histograms on mobile. r=vladan (911084001c) - missing bits of Bug 1023461 - Add HangStack class to support internal string buffer; r=vladan (599bee2150) - Bug 1196381 - Eliminate breakpad dependency in ThreadStackHelper; r=nfroyd r=snorp (ff8a632975) - fix misspatch of 1157282 and 1198883 (9a216ab188) - Bug 1034138 - a. Get native stack for permahangs in BHM; r=snorp (772970d0e0) - Bug 1211411 - Limit the number of thread hang stats reported to Telemetry. r=vladan (fd72bc8b62) - Bug 1219751 - Change the the depth limit of the thread hangs stack to use the 99th percentile. r=gfritzsche (fc59bd7598) - Bug 1133521 - Enable BHR on Beta. r=vladan (2501c6a0ff) - Bug 1219216 - Fix a wrong comment in BackgroundHangMonitor.h. r=gfritzsche (e974320361) - bits of Bug 1134279 - Change Telemetry data producers to use the correct (d00e84b7f3) - bits of Bug 977026 - Part 2: B2G loader (bf1208a73a) - bug 1198450 - Firefox fails to load about:home if Firefox was installed to a folder with non-Latin name r=jimm (c4df06a69e) - Bug 1222167 - fix initialization order in GeckoChildProcessHost; r=jld (6bad274479) - Bug 1141693 - Build and use a PIE plugin-container on Android 5.0+. Based on a patch by Mike Hommey. r=me,glandium (78dc877aec) - Bug 1187533 - Change how Gtk+2 plugin-container is started on Gtk+3 builds. r=billm (93c2b8a1b0) - Bug 1063359 - Unconditionally use -Wl,--no-as-needed when building with GNU ld/gold. r=mshal (643e92ca49) - Bug 971811 - Don't prepend an empty existing DYLD_INSERT_LIBRARIES path when launching the plugin. r=smichaud (c72df0073c) - Bug 1189352: Fix NSPR_LOG_FILE with absolute paths for sandboxed child on Windows. r=bbondy (f4bb51c123) - Bug 1189967 - Be slightly more explicit about some conversions to std::wstring. r=nfroyd (7bec611359) - Bug 1201438: Add non-sandboxed Windows content processes as target peers for handle duplication. r=bbondy (1ca7f499e9) - Bug 1201438 - Fixup for builds with disabled sandbox. (de125d156e) - Bug 1165895: Add NPAPI sandbox rule for the crash server pipe and x64 Temp dir write access. r=bbondy (e9f601912d) - Bug 1202988 - Don't use GetTempPath for flash's mms.cfg hack for low integrity. r=aklotz (b4a0d7f856) - Bug 1225023: Allow Flash Player to create Adobe\Flash Player and Macromedia\Flash Player directories. r=bbondy (c5120afc1d) - Bug 1218681 - add plugin-container standalone process code. The Code associate with ARCH. r=hev (03dfb21776) - bug 1130976 - Flash context menu causes CPOW deadlock with AdBlock Plus, plugins should spin even loop in content process instead of the chrome process r=billm (52f4d33633) - Bug 1157237: Move invocation of async NPP_New to an async task; r=jimm (7b6c1a577e) - Bug 1175147 - Don't do threadsafety asserts for NPN_MemAlloc and friends, r=jimm (b4ce5b33ce) - fix strange misspatch (8a96a61819) - Bug 1219244 - use UniquePtr instead of nsAutoArrayPtr in dom/plugins/; r=aklotz (19fabc55b5) - Bug 1155503: BrowserStreamParent should null out its NPStream pointer and we should check for it; r=jimm (eddb82b8b4) - some crashrep stuff (bb2b046090) - Bug 1192077 - Convert AndroidBridge JNIEnv calls; r=esawin (821453089e) - Bug 554171 - Add plugin thread checks to functions that must only be called on the main thread. r=jimm (f2eb3822da) - Bug 1149358: Ensure that plugin streams are not manipulated by PluginAsyncSurrogate if plugin destruction is imminent; r=jimm (6dd99c94ee) - Bug 1198302 - Ensure that PluginAsyncSurrogate::NotifyAsyncInitFailed properly aborts any PluginAsyncSurrogate::WaitForInit calls. r=jimm (23c1fbfcfe) - Bug 1201239 - Add a proper null check in PluginAsyncSurrogate::NotifyAsyncInitFailed; r=jimm (5d8ff9f8aa) - Bug 1208059: Make nsNPAPIPluginInstance support WeakPtr and modify PluginAsyncSurrogate to use it; r=jimm (174a3166b1) - Bug 1171453: Make ParentNPObjects aware of AsyncNPObject wrappers; r=jimm (92e608831d) - Bug 1217726 - Fix -Wimplicit-fallthrough warnings in dom/plugins. r=jimm (32db26ede8) - Bug 1167720 - Fix invalid window ID provided to GTK3 plugin container children. r=karlt (d8c2de0c19) - Remove Windows-specific synchronous plugin drawing code. (bug 1218688 part 1, r=jimm) (5e4b60ea33) - Remove Linux-specific synchronous plugin drawing code. (bug 1218688 part 2, r=jimm) (edb29f27b8) - Remove Mac-specific synchronous plugin drawing code. (bug 1218688 part 3, r=benwa) (acc6b57b23) - Assert that we do not attempt synchronous painting of windowless Desktop plugins. (bug 1218688 part 4, r=bsmedberg) (c34094b038) - Bug 1195472 - Call Show after Enable on puppet widgets to avoid an assertion when running crash tests. r=aklotz (405ed2c1d1) - Add explicit keyword to AsyncScrollBase constructor to fix static analysis build (bug 1139220 part 6, r=shu) (4cc37b9a3b) - Bug 1146561 - Add back the visibility check for Mac plugins. r=jmuizelaar (91a4a5a8e9) - namespace (9b4919f8fa) - Bug 1217307 - Remove some unnecessary null checks in rest of dom/. r=njn (de5d69880a) - Bug 1225137 - Avoid crash on some platforms if scrollbar fading is enabled and the duration is set to zero. r=spohl (a16954de2f) - Bug 1114554 - Disable NotificationStorage debug logging. r=dholbert (c2722fa4ed) - Bug 1073551 - fix doorhangers to not steal focus unless explicitly opened using mouse or keyboard, r=jaws (be6109cf6d) - Bug 1169629: Add-on install confirmation notification appears anchored to older dismissed anchors. r=dao (684535c7cc) - Bug 1194706: make sure that the notification icons and doorhangers are shown in undocked chat windows too. r=Mossop (68e0ced913) - Bug 1207089 - Telemetry for permission notifications. r=MattN,vladan (ff421236ea) - Bug 1215526 - part 4 - make preprocess-tab-svgs.py report extra dependencies; r=glandium (98b64b5c45) (4e6138a54f)

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20230225-3219d2d-uxp-ba020f4a7-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20230225-3219d2d-uxp-ba020f4a7-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.rthost.win/basilisk/basilisk52-g4.8.win32-git-20230225-3219d2d-uxp-ba020f4a7-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.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230225-d849524bd-uxp-ba020f4a7-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230225-d849524bd-uxp-ba020f4a7-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230225-d849524bd-uxp-ba020f4a7-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20230225-d849524bd-uxp-ba020f4a7-xpmod.7z Official UXP changes picked since my last build: - Issue #2107 - Clean up caret when destroying editor. (cc6b0f11e) - [widget] Properly test for and handle errors in target-surface creation and mapping. (bca689b48) - [DOM] Check whether module load request was already cancelled when a load fails (bc50a7d3c) - [NSS] Update NSS to pick up fixes. (cdda874cf) - Issue #2046 - Move ScopedICUObject into builtin/intl/ScopedICUObject.h (017261964) - Issue #2046 - Move functionality used in the implementation of multiple Intl.* constructors into builtin/intl/CommonFunctions.* (50e3c1f5e) - Issue #2046 - Create helper method to call ICU string conversion methods (eee13d265) - Issue #2046 - Move Intl.NumberFormat functionality into builtin/intl/NumberFormat.* (e7565ff1a) - Issue #2046 - Move NewUNumberFormatForPluralRules next to its only use (6da7d528d) - Issue #2046 - Move Intl.Collator functionality into builtin/intl/Collator.* (53c2f58c5) - Issue #2046 - Move SharedIntlData into its own builtin/intl/SharedIntlData.* files so the world doesn't have to import all shared Intl functionality. (ce98604d2) - Issue #2046 - Move Intl.DateTimeFormat functionality into builtin/intl/DateTimeFormat.* (c981fb13e) - Issue #2046 - Move Intl.PluralRules functionality into builtin/intl/PluralRules.* (ed316832b) - Issue #2046 - Move Intl.RelativeTimeFormat functionality into builtin/intl/RelativeTimeFormat.* (c7dab6c03) - Issue #2046 - Trim builtin/Intl.*'s #include set down to what is required for Intl itself (5ad62567e) - Issue #2046 - Move builtin/Intl.* to builtin/intl/IntlObject.* (5574b06ff) - Issue #2046 - Move various generated files from builtin/Intl* to builtin/intl/*, and add "Generated" to their names for clarity (f8e3f8119) - Issue #2046 - Move the self-hosting of non-constructor properties of Intl to a new builtin/intl/IntlObject.js file (7f2b67f7d) - Issue #2046 - Move Intl.RelativeTimeFormat self-hosted code to a new builtin/intl/RelativeTimeFormat.js file (ae0eddc16) - Issue #2046 - Move Intl.PluralRules self-hosted code to a new builtin/intl/PluralRules.js file (e55cdd19a) - Issue #2046 - Move Intl.DateTimeFormat self-hosted code to a new builtin/intl/DateTimeFormat.js file (38284ba8b) - Issue #2046 - Move Intl.NumberFormat self-hosted code to a new builtin/intl/NumberFormat.js file (a56b9e832) - Issue #2046 - Move Intl.Collator self-hosted code to a new builtin/intl/Collator.js file (45720521c) - Issue #2046 - Move builtin/Intl.js (which now contains only shared functionality) to builtin/intl/CommonFunctions.js (cf2e2ed90) - Issue #2046 - Move a bunch of functions in builtin/intl/CommonFunctions.js into more-specific files, where those functions are only used in a single more-specific file (87eaaee95) - Issue #2111 - Implement CSSStyleRule.selectorText setter (6d3500bb4) - Issue #1382 - Annotate crash with database name when storage connection not closed (6dc8a7d81) - No issue - Improve fallback handling and resolve PATH issues with python clobber command (b7d80962d) - MailNews: Re-check availability of OAuth2 when hostname fields modified. (e8f840bf2) - Issue #2078 - Part 1: Update CSS rule processor to handle :is() and :where() CSS pseudo-classes (453b715ef) - Issue #2078 - Part 2: Rename nsPseudoClassList->u.mSelectors to mSelectorList (0648ec64b) - Issue #2078 - Part 3: Rename nsCSSRuleProcessor::SelectorListMatches to RestrictedSelectorListMatches (14e8922dc) - Issue #2078 - Part 4: Unify selector list matching (1c1473166) - Issue #2078 - Part 5: Ensure :is() and :where() are given proper weights (4ece7873e) - Issue #2078 - Part 6: Replace empty list head with the next non-empty list for forgiving selector lists (6d77f755d) - Issue #1823 - Ensure :host() and :host-context() are given proper weights (ba7e29a05) - Issue #1593 - Follow-up: :host() should not automatically match if we have a non-empty selector list (9bebb3a61) - Issue #1593 - Follow-up: Copy mIsRelevantLink value over rather than calling IsLink (0391e8ab0) - Issue #1593 - Follow-up: Accept only a single selector in the argument of :host/:host-context (9037d5662) - No issue - Refactor FindErrorInstanceOrPrototype (db89c5a05) - [DOM] WebCrypto: Check decoded key type before using it. (0b9698c80) - No issue - Move Has* function definition out of the header file for consistency (03a338570) - Issue #2078 - Follow-up: Move isForgiving check to ParsePseudoClassWithSelectorListArg (53f590538) - Issue #2078 - Follow-up: aPreventComplexSelectors should be passed (83484a34f) - Issue #2078 - Follow-up: Propagate combinator restriction to :is()/:where() (439c671b2) - Issue #2046 - Follow-up: Fix debug assert using old chars definition. (fa014f9e9) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. Update Notice: - You may delete file named icudt58l.dat inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

a: UXP based applications have 2 parts: front-end and UXP engine. front-end code doesn't change frequently (or say, "at all" for BOC related) b & c: IceDove and IceApe is hyperbola's port/rebrand of Thunderbird and Seamonkey to UXP.

Agreed. I prefer .zip versions also.

I'm sure you've read the forum rules, specifically Rules 1 and 4e (to cover the bases).

Also a new release by Feodor2 just 14 hours ago. MyPal68.13 nightly build https://github.com/Feodor2/Mypal68/issues/160 It is supposedly even less stable but has better JS engine, I suggest to check it out.

By any chance, you aren't under the influence of chemical substances, are you ?

Right. Security holes in Chromium 86, which this browser's based on, are there by definition.

Empty promises again ? I'm timing you. If by that time you don't release it, I'll report you to the imperial guards.

Well, Chromium is using Windows 10 titlebar, and it doesn't render properly. You can disable Windows 10 titlebar by adding --disable-windows10-custom-titlebar to the "Target:" textbox of Chromium's desktop shortcut.

Absolutely, completely agreed. Actually, I just upgraded to v96 and I find it to be a solid improvement over v90. You made a believer out of me on this one--I've decided to 'cheat' a little bit and stay with v96 for the time being. I believe there is truth to the '20 versions' rule and I'm sticking with it, but I'm going to let it kick in when the stable version is up to v117 (at which time I'll move up to v97 and just keep going from there). In general, that rule keeps you more or less 2 years behind the latest release, which seems to be as far back as you can go and still have that 95% compatibility with the modern Internet. That percentage drops if you keep a version that is too old, but I do think that older versions are still worth tinkering with (as they tend to have a lot of interesting/useful features that were taken out of later ones). Hopefully the speed and performance will stay on the road it's on, but either way once v117 is out, I'm moving to v97 and staying 20 behind the latest from then on. It's going to be a long time before I will need to worry about it, presuming the speed drops in the future. UPDATE: As of the time of writing, I have moved back to Windows 7 x64. I actually enjoyed getting a feel for what to expect with 10 in the future...but there is nothing that really seems to necessitate the jump to 10 right now. 7 seems to be the best 'bridge' between XP and 10, with a kernel that is closer to 10 but performance that is comparable with XP (and better compatibility with 'legacy' hardware & software). It runs a lot better than 10 on the same hardware, but 10 honestly wasn't performing that badly (so I do feel optimistic for the future). Right now, the plan is to stay with Chromium 96, make the jump to 97 once 117 is the newest stable, keep going version by version until we get to the 109/129 milestone, and then maybe I'll switch over to Firefox once 130 is the newest stable Chromium (again, 20 versions rule...whatever Firefox version is the current, be 20 versions behind it). Hopefully Firefox is still going to be supported by Mozilla by then...if not, I'll keep going until I reach the inevitable dead end and then either stay with Firefox indefinitely or look at the other options that are available by then. I have a feeling Windows 7 should be usable for the rest of the decade, and then maybe in the 2030s I'll have to make the switch to 10.

Since I don't know whether the guys (and girls?) from WiseVector have finally given up on their WiseVector StopX program or not, I have first completely deactivated it in my system, i.e. deactivated autostart of the program and its system service. Perhaps, they will reconsider their decision. After a deep research, I decided to give Panda Dome 22.00.00 a chance. This version is the most recent and fully compatible with Windows XP. Here are two screenshots of Panda Dome: So far, I am quite enthusiastic. The system load of Panda Dome is very low (lower than it was with WiseVector StopX), and the detection rate is supposed to be very good according to my research. I will keep you updated. Cheers, AstroSkipper

Not all 109 versions work. The later "final releases" - don't. Tht last working one was 109.0. 53.97, if I'm not mistaken. Some kind fella created a list of the last versions in the last win 7 soft topic. Some manufacturers stopped even at 108 or so.

Windows 7 Pro 64bit forever!!! I just joined this forum & am watching this thread with great interest, especially @msquidpl's posts. A browser is my one concern because browsers are major entry points for malware. However, I surf the internet while in Shadow Defender's "Shadow More" -- it's like a virtual computer -- so a permanent infection is extremely unlikely. Even so, an updated browser for Win7 would be delightful. My Plan B is Zorin Linux Pro -- it's very similar to Win7 & I am getting fairly proficient with it. Aloha to all from Hawaii... bellgamin

I quite agree that no one is going to read a 76-page thread (which will soon reach 77 pages at this rate). On the other hand, replying to a thread (particularly this one) without looking at the original post only causes further unnecessary lengthening, so thanks for nothing!

Would be interesting to try this browser out with the updated chrome 112 engine ! 86 seems a bit out of date, just a bit.

Better she get Vitamin C, Vitamin D, and Ivermectine, so no problem.

Hello, MSFN! So, a few days ago I got the idea to put Vista on my Dell Inspiron 3880. Due to Vista releasing way before UEFI started being used, Vista simply does not boot on a Class 3 system. I have tried UEFISeven... but ummm... yeah it doesn't work. Just a black screen. So, I was wondering if anyone here had any suggestions to get Vista on my computer. Yes, I know my PC is new, and that Vista is old, but in fact I'm typing this on Windows 7 on said system. If you know a way to get Vista on Class 3, please let me know. I have tried the following: -UEFISeven -Windows Vista on its own bootloader ...yeah that's it. While I'm posting about Vista, I might as well talk about potential needed drivers if anyone has been able to mod them. Most notably, the Intel Wireless AC-3165 and the Intel UHD Graphics 630*... which both are usable on Windows 7 So if anyone could help me, that'd be awesome, however I'm keeping low expectations for now. Thanks everyone in advance!

Now that reboot.pro is online again, here is the thread about GOP hardware and windows 7: http://reboot.pro/index.php?showtopic=21108 Maybe useful, maybe not. jaclaz

How to install Office 2013 on Vista 1- Have a copy of Office 2013 64-bit handy (The latest extended kernel is needed, x86 is useless) 2- Copy to the desktop in a new folder the root of your copy of Office 2013 3- Copy the ProPlus.WW.en-US folder to the desktop (the name may vary due to the language/edition of the copy), this is important since the Office installer detects the edited files and the installer of this folder needs to be edited. 4- In the folder copied to the desktop open ProPlus.WW.msi with Orca, go to InstallExecuteSequence and remove AbortMsi (it blocks the installation outside of setup.exe that verifies the files), then in Components change all Conditional VersionNT >= 601 by VersionNT >= 600. 5- Replace gdiplus.dll with the one from Windows 7, this is the path in the system: C:\Windows\winsxs\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6002.19749_none_56a723b1b598503f\gdiplus.dll 6- In group policies of the local machine, it prohibits rollback (very important) 7- Create an osver.ini file with the following settings (required at all times when installing Office 2013): [global] MinorVersion=1 BuildNumber=7600 8- Open ProPlus.WW.msi and after installation the Office 2013 suite should appear in the start menu, but it is not enough! 9- Go back to group policies and disable rollback, but keep osver.ini 10- In the root folder of Office 2013 the only change we will make is to delete the update or updates folder, they cause bugs when installed 11- Open the setup.exe of the normal Office 2013 installer and customize it to your liking (it should install successfully, if an error appears, reboot the system) 12- Open Word 2013 (it can be any program in the suite except Visio, Lync, InfoPath or Outlook) to configure Office 2013 13- The programs of the Office 2013 suite will need to be detected at all times as Windows 7 or an annoying Windows Installer dialog will appear configuring each time the program starts: [C:\Program Files\Microsoft Office\Office15\EXCEL.EXE] Enabled=1 Win7SuperVerFix=1 MinorVersion=1 BuildNumber=7600 [C:\Program Files\Microsoft Office\Office15\MSACCESS.exe] Enabled=1 Win7SuperVerFix=1 MinorVersion=1 BuildNumber=7600 [C:\Program Files\Microsoft Office\Office15\MSPUB.exe] Enabled=1 Win7SuperVerFix=1 MinorVersion=1 BuildNumber=7600 [C:\Program Files\Microsoft Office\Office15\ONENOTE.exe] Enabled=1 Win7SuperVerFix=1 MinorVersion=1 BuildNumber=7600 [C:\Program Files\Microsoft Office\Office15\OUTLOOK.exe] Enabled=1 Win7SuperVerFix=1 MinorVersion=1 BuildNumber=7600 [C:\Program Files\Microsoft Office\Office15\POWERPNT.exe] Enabled=1 Win7SuperVerFix=1 MinorVersion=1 BuildNumber=7600 [C:\Program Files\Microsoft Office\Office15\WINWORD.exe] Enabled=1 Win7SuperVerFix=1 MinorVersion=1 BuildNumber=7600 14- ¡Enjoy Office 2013! SOMEONE BUGS 1- A large part of the office suite worked without problems, but there are programs that have some problem to solve: Outlook: won't start due to missing dependency on advapi32.dll (in future extended kernel updates this may be fixed) Lync: Stop responding... on welcome screen Infopath: Won't even open Visio: When creating a new drawing stops responding 2- It is impossible to activate it (at least there is no time bomb) 3- Can't login (maybe because of TLS) CONCLUSION We have partly killed the obsolescence imposed by M$ in Vista, which only received two versions of Office. Almost the entire suite works perfectly under Vista, except for Lync or InfoPath that I don't find useful, Outlook and the lack of dependencies in advapi32.dll. In the usual programs like Word, Excel or Powerpoint I can do anything without problems as if I were in Windows 7 or 8.