Mathwiz

Well, that explains the otherwise odd-seeming upping of the required minimum from 113 to 115, at least, if it's the last Win 7-compatible version. In any event, Chase lowered the boom rather quickly this time. I can no longer sign in using either Serpent or 360EE. There appears to be a JSON parsing error in my Chase-specific StructuredClone polyfill. @UCyborg's more sophisticated polyfill doesn't do the trick either since it doesn't handle self-referential objects (same problem as with the StructuredClone built into UXP). Also not working: Chrome 106 on Android 6.0. Edge 109 (on Win 7) still works (so, I assume, Chrome 109 would too), but for how long? It too now has the ominous "We'll stop supporting this browser soon" nag. FF 115 ESR will presumably have a somewhat longer lifespan, but the end is in sight there too. Looks like it's gonna be Thorium and/or Supermium in my future, whether I like non-unGoogled Chromium derivatives or not. I appreciate your honesty; but I daresay your "not-so-humble" opinion very likely puts you out of step with the vast majority of MSFN members. Yes, I know you "upgraded" to Windows 10 and are currently using Chromium 114, so perhaps you don't care what happens to those of us who still use earlier Windows versions (even 8.1); but there will come a day when your OS/browser will stop working too, at which point I will be overjoyed to remind you of your "not-so-humble" opinion! I just rename the folder; e.g., rename "New Moon" to "Old Moon" (delete the "Old Moon" folder first, if it still exists from the last update) and restore the new version into a new "New Moon" folder. I even wrote a batch file that automates the process. You don't lose any settings (unless you made your New Moon installation portable). Yes, I noticed that too, some time ago. It's a longstanding bug that also affects the pages shown by long-clicking the Back button. I just decided to live with it. I think their discussion was specifically about DNS over HTTPS, which wasn't a thing until long after XP EOS. Unfortunately, not likely, given MCP's position: DoH is a double-edged sword. It can be used to conceal your browsing habits from your ISP (probably a good thing) but it can also be used by apps to thwart ad blockers like Pi-Hole, which most users would consider a bad thing. But as usual, MCP fails to understand that their decision not to support DoH will have exactly zero effect on its "bad" uses coming to fruition; all it does is mean that Pale Moon users can't easily avail themselves of its "good" uses. (The apostrophe - D'OH - was clever though.)

https://www.tomsguide.com/ looks to me like that stupid link rel="preload" issue we also see at Micro$oft's Web pages. Proxomitron and/or Modify HTTP Response might be able to fix it. Someday I'll find the person who came up with that "preload" nonsense and wring his neck. AFAICS it accomplishes nothing other than breaking Web pages on older browsers. OTOH, I cannot understand why MCP still hasn't addressed link rel="preload" in UXP. It's been an issue for a long time, it breaks major sites like Micro$oft's, and (although I'll admit I don't know enough to be sure) it doesn't seem like something that would be all that hard to implement.

To me, that indeed sounds like the most plausible explanation, especially considering that they did not increase the minimum version for Chrome/Edge! Although if "security" is the reason, I would've expected them to require at least the WebP fix, which V115 lacks.

Hi folks! My bank's site, chase.com, is once again upping the minimum browser version for Firefox. (This hasn't yet been implemented. At this point, a nag appears if your user agent reports a version that's "too old," but everything still works - for now.) The last time they did this, they raised the minimum to v113, and I changed my user agent to match that minimum. This time, they're raising it to ... v115. Setting the user agent to v115 or later removes the nag. I was flabbergasted! I half expected v117, the last version for Windows 7, at least. What's the point of raising the minimum by a mere two versions? What did FF v115 bring to the CSS/Javascript table that Chase just had to have? I'm anticipating a future breakage of chase.com with bated breath.

From the r3dfox readme:

I hate things like that. Whose side is the browser on, anyway? If it can download an image for display, it should be able to download the same image to disk. Win 7+ (maybe Vista too; IDK) have a "snipping tool" you can use to save images, but I don't know if there's an XP app that does something similar.

Here's part of what @VistaLover wrote recently about NM 27 vs. 28. Actually this was in the context of discussing why we were getting so many NM 27 updates:

Forum search functions generally suck - not just ours but every one I've ever tried. What would be really helpful is Bing's new AI search - just type in the question, et voila! But you have to be running Edge to use it and if you're able to do that, you probably aren't interested in NM 27 or 28!

Agreed. I wasn't casting aspersions on the user for asking - that was the right thing to do. Just pointing out that the question does come up a lot, and will probably continue to do so. Rather than a long response, it would probably be easiest to beef up the FAQ with links to one of @VistaLover's detailed replies on those two topics. I wouldn't use it, but it (and its sister K-Meleon) are more lightweight than current UXP browsers, so they might be reasonable "first browser" choices on older hardware where UXP is unacceptably slow. If it fails to render a site properly you could always fire up Serpent, go make a cup of coffee, drink it....

There's a thread on Supermium here at MSFN: https://msfn.org/board/topic/185045-supermium/

That question comes up so often, it probably should be addressed in the FAQ at the beginning of this thread.

Agreed; it's your Dropbox account and you can put what you want there. But folks will keep finding this thread, and this will repeat, unless you at least remove the dead links from post 1. Also, if you follow the quote above back to the original post, you'll find a link to build 2036, whose links are also dead. Please don't frustrate new would-be users! If it were me, I'd not only remove all those dead links, but also replace them with a link to the redux thread so folks can download the "newer, improved" version. Unfortunately I doubt there's much more that can done with 360EE. I'm just happy we have a reasonably modern (at least when beefed up with polyfills), lightweight, unGoogled Chromium for XP.

Is this where the "Offline Web Content and User Data" shown when you go to Tools / Preferences / Advanced is stored? I think logins and passwords are stored in a different table, but I'm not sure.

Wow - it's good to be back after that scary outage! Also good to see that nothing appears to have been lost. It's been 2 1/2 weeks since I posted about pdf.js; unfortunately I was stopped by a problem I couldn't resolve and had to go back to the drawing board. Although the pdf.js V2.15 I downloaded from GitHub works fine with some sites, it simply won't work with others. Problem is (or at least appears to be) that the downloaded version was intended to be hosted on a Web site, not run from within the browser (either built-in or as an extension). As a result, Serpent's cross-site scripting protection keeps kicking in if the site you're trying to download a .pdf from doesn't send the right "CORS" header saying it's OK for another "Web site" to access the pdf. I couldn't figure out how to get around it, so I gave up on the GitHub versions. Instead I started extracting pdf.js from newer versions of Firefox. This worked better, without the XSS errors I was getting with the downloaded versions. I got up to FF 79, but that was still only at version 2.6.47. (Unfortunately Mozilla shuffled everything around in FF 80 and I haven't yet found the pdf.js in that or any newer version.) So, a disappointing setback, and RL issues haven't helped. But I haven't given up yet.

I hear you. But I still update more often than once every five months! I believe the 2-24 Serpent versions are stable and that's what I'm running now. There have been no updates in several weeks, long enough to identify and fix any big issues.