Jump to content

Mathwiz

Member
 View Profile  See their activity

  • Posts

    1,867

  • Joined

  • Last visited

  • Days Won

    51

  • Donations

    0.00 USD 

  • Country

    United States

 Content Type 

Everything posted by Mathwiz

  1. Mathwiz
    I suspect @looking4awayout's UOC patch. The way it's installed (copy to defaults\pref subdirecory), it affects all profiles, including clean ones. I reinstalled the 2022/05/06 version without the UOC patch and the button icons are normal. Now I just have to find out which of the many, many prefs changed by the UOC patch suddenly started malfunctioning in the 2022/05/06 version....
  2. Mathwiz
    Yes it does: "Safe mode" doesn't solve the problem either.
  3. Mathwiz
    Some button icons seem messed up in the latest (2022-05-06) St 55: What it looks like in earlier versions (this is from 2022-04-29):
  4. Mathwiz
    Hey - I expect to be in my 3rd or 4th robot body by then!
  5. Mathwiz
    What is it with us programmers anyway? Not only do we have to mess around with a perfectly reasonable programming language, thus requiring constant browser updates, just to save a few keystrokes on occasion.... ... we also have to make up new words just to describe what we're doing!
  6. Mathwiz
    Now that I think about it, I started using this feature on St 52 (where it has always worked), because until recently, there wasn't a big need for me to launch single-process mode in St 55. (The only real use case for me was Classic Add-Ons Archive, which does the trick on its own on both 52 and 55, once patched to treat Serpent like Waterfox). It wasn't until your recent work on St 55 enabled use of the gh-wc-polyfill add-on that I had a need to launch single-process mode on St 55. By that time, the only versions I had on my PC were 4/1 and 4/15, so those were the only ones I tried.
  7. Mathwiz
    And to think many folks used to spoof FF 99 to "future-proof" their UA spoof. So, FF has finally caught up to Chrome version numbers. (Well, almost. My BlackBerry Priv is at Chrome V101.) Congratulations Does that mean they're going to slow down their version cycle now to stay in sync, or does that mean Chrome is going to speed up theirs? Oh, well; at least we can look forward to this: in another 160 years or so, both versions should catch up to the actual year, and they can finally drop all this silliness. The irony of all this is, it won't even work for its stated purpose; at least not for long. The spammers will quickly update their bots with the latest Chrome JS engines, and be able to pass the challenge. Surely Cloudflare and Gitlab know this; Chromium is open source, after all. News flash: humans (even this one) are not good at "mathematical challenges!" The only way to truly block bots is with an interactive captcha, which users understandably despise. So the only net effect will be to block folks from signing in unless they use Google's latest spyware er, "browser." (BTW, I wouldn't be surprised if common privacy protections, like canvas fingerprinting blockers, also stop you from getting past the Cloudflare "challenge." And don't even think about NoScript....) A better solution would be to just offer a captcha if the browser fails the "challenge;" that way you could still sign in with a non-evil browser, albeit with more annoyance. At least it still works (for now) in 360EE v12. I suppose there's a nonzero chance that UXP will get up to that level (and can then pass with a UA spoof) before Cloudflare updates their challenge to only work in Chrome 98+.
  8. Mathwiz
    Search bar works in the latest St 55, though, in case that helps with debugging.
  9. Mathwiz
    Here's something I never thought I'd see: e10s in NM 27? We don't even have that in NM 28!
  10. Mathwiz
    Ran into an obscure bug in the 4/1 and 4/15 Serpent 55 releases: on the about:profiles page, if you try to use any of the "Launch Profile in new browser" buttons, they don't launch the selected profile. They all launch the default profile instead. Thus, to switch profiles on Serpent 55 you much change the default profile, restart, then repeat the process if you want to go back to your original default profile. I use this as a quick way to get out of multiprocess (e10s) mode when I need to use an e10s-incompatible extension like github-wc-polyfill, so this bug makes that process rather cumbersome. The latest Serpent 52 doesn't have this bug; the "Launch Profile in new browser" buttons work correctly there.
  11. Mathwiz
    Thanks for the tip; I'll give it a try!
  12. Mathwiz
    Thanks @roytam1! That's a huge list of changes and it's only been 2 weeks since the last Moebius update! You've been very busy, it seems. I'll download and give it a try. Very recently, chase.com made some Javascript changes that (you guessed it) broke their site on both UXP and Moebius browsers. There are no visible changes to the site; it just quit working on non-Chrome browsers. (To be fair, the site's performance on 360EE is greatly improved over how it was when it did work on all these browsers, so the majority of the site's users who do use Chrome are probably pretty happy with the changes.) Edit: Just tried it, and chase.com works again! It's not as fast as it is on 360EE but it's adequate. Besides, Serpent auto-fills my user ID and password; 360EE won't for some reason.
  13. Mathwiz
    Yes; IIRC, there was no iPhone 9 either! In Apple's case, they were in a hurry to get to 10, because the Roman numeral for 10 is X, and they wanted to advertise the "iPhone X" (as in Xtreme, I suppose) But I don't recall M$ ever advertising Windows 10 as "Windows X" or some such nonsense. Anyway, I hope you're right that the 360EE version is now the year (on the Gregorian calendar) - I just wish M$, Mozilla, and Google would follow suit! <off topic>My sincere apologies for trying to dissuade @InterLinked from buying an automobile from the era when gasoline in the US still had lead in it (not to mention wishing I could buy an unGoogled EV) - that one comment once again derailed the entire thread with a raft of political propaganda. You'd think I would've learned by now!
  14. Mathwiz
    In this case, I'd urge you to rethink that position. Dependence on gasoline (or petrol, as some call it) is becoming increasingly untenable in the modern world, for many good reasons. I do, however, share the reluctance to get one of these "Google-enabled" cars, just to get an electric model. Can I get an electric car without the spyware, please? Unfortunately I think the 360EE developers have already announced that the next version won't run on XP. Heck, we're lucky it runs on Win 7, given that Google has already given up on that platform. What happened to versions 14-20?
  15. Mathwiz
    I should've used scare quotes, as you did I agree with you. Nothing made in 2015 should be unusable a mere seven years later. Heck, this thread is in a section of MSFN dedicated to OSes much older than that; yet we manage to keep them going.... Yet phones are an even bigger planned-obsolescence racket than PCs. I could go on and on about the hoops I had to jump through to keep a 7-year-old phone operating. It's AT&T-branded, yet AT&T's SIMs won't enable voice over LTE on it, which is needed now that AT&T shut down their 3G network. So I had to switch my AT&T phone to another carrier to use a feature that AT&T built into it in the first place! Yes, I was referring specifically to digital cell phones. I too have an old AT&T rotary dial phone that still works on the modern PSTN. But I'm getting way off-topic here, so I'll shut up....
  16. Mathwiz
    Could be deliberate, in order to force use of the "latest" browser versions, for "security" I feel fortunate that Chase.com still works in Serpent (52 and 55) as long as I use a user agent spoof, and of course don't try to enable "Web Components." On Android, not so lucky; I have a "vintage" 2015 Android phone which still works (even survived AT&Ts shutdown of their 3G network) except for the Chase app. The last Android 6 version of their app has been blocked for many moons. Never mind; I can still use Chrome - oh wait, Google just stopped updating Chrome on Android 6 too, so those days are numbered too. At least I got all the way up to Chrome 99 first (maybe Android 6 can't handle a 3-digit version number ) Assuming the phone continues to hold out, my last resort will be Firefox (probably FF 56 with, you guessed it, a UA spoof).
  17. Mathwiz
    Since this error appears to be related to missing Shadow DOM support, I'm testing in St 55.... BRB.... Well, that was sort of a bust. Couldn't really test anything since I'm not a Comcast customer (thank goodness), so no signing on for me! I'm guessing @Art7220 couldn't sign in with the pref disabled, got further with it enabled, but gave up because setting the pref broke YouTube (a la my experience with Chase). Be interesting for a Comcast customer to try this and see what the issues are with the pref disabled and with it enabled, not only in a UXP browser like NM but also in St 55.
  18. Mathwiz
    I had my suspicions; after all, it's intended to test whether or not a feature is implemented; it isn't an exhaustive test of whether a feature is implemented correctly. It's all I had to go on, though. So, St 52's implementation of Custom Elements is still incomplete. It's probably the best we have until Moonchild puts some effort into it, though. As for Shadow DOM, html5test.com claims St 52 has partial support, and that St 55 has full support. We'd probably need to scour Bugzilla for relevant code (and might, perhaps, find more relevant usable code in FF 54 and 55. I doubt anything later could be merged into either Serpent version though). BTW, it turns out that setting dom.webcomponents.enabled breaks Chase.com in St 52 too, although it's not as badly broken as in St 55. Apparently the site is designed to work correctly if someone disables Web Components, but otherwise it expects a complete implementation. So my advice now is to leave the pref off in both browsers. If anyone discovers a specific Web site that only works with the setting enabled, make a copy of your main profile, and just toggle that pref on in the copy, so you can use that profile for the site that requires it. (Let the rest of us know what you find too.)
  19. Mathwiz
    I don't think Mozilla got Web Components quite right until well into the Quantum era, but there is hope! Per HTML5test.com, latest St 52 has full Shadow DOM support (I'm guessing thanks to MCP) but lacks Custom Elements support, while St 55 has Custom Elements support but partial/broken Shadow DOM support, both probably inherited from FF 53. So perhaps we could port the changes for each into the other and get full Web Components support in both versions. Web Components are only one piece of the current JS issues, but it seems like it's worth a try.
  20. Mathwiz
    It's worse than that. I just found that setting either pref on Serpent 55 breaks chase.com. I'm guessing that chase.com checks whether these features are enabled and tries to use them if present, but runs fallback code if they're not. (Surprising when so many sites just expect them to be fully implemented.) If 55's Web Components implementation is incomplete and/or buggy, then enabling either pref actually makes things worse.
  21. Mathwiz
    On Serpent 55 enable that pref and dom.webcomponents.customelements.enabled too. This is probably the closest you can get to Web Components support on any of @roytam1's browsers (too bad 55 has fallen behind in other JS areas):
  22. Mathwiz
    Besides Notepad++ (which is great), Micro$oft's Wordpad, which comes with WinXP, works just fine. I use it all the time for these install.rdf fixes. Notepad will work too, but if the install.rdf has only LFs (not CR+LFs), then the lines of text will all be smushed together, making it very challenging to edit! Wordpad handles text files with only LFs much better. BTW, here's a trick I use: install 7-Zip, set up Wordpad (or Notepad++) as 7-Zip's default text editor, then use the "Open With" dialog to associate .xpi files with 7-Zip. Now you can open them by simply double-clicking, edit the install.rdf by clicking it and pressing F4, and when you close Wordpad and save your changes, 7-Zip will prompt you to update the install.rdf file inside your .xpi file automatically - no more need to extract, zip back up, and rename! Great time-saver.
  23. Mathwiz
    That one confused me until I looked it up on Wikipedia. Who in their right mind would encode a date in a format that only spanned the 22 years 2000-2021? Well, nobody, of course - so naturally Micro$oft did just that, in their Exchange email product! For us aficionados of older OSes, the "big one" is probably 2036, when NTP rolls over. I doubt even Windows 10 will get an update for that one! Luckily, we should all have a 3rd-party NTPv4 client by that time. The thing that annoys me about this one is, NTP uses a 64-bit time value, but splits it into two 32-bit parts: the first for the number of seconds since 1900 (what were they thinking?) and the second for fractions of a second, down to a resolution of 233 picoseconds, the time it takes light to travel about 7 cm. If they'd just started NTP at the GPS epoch, we'd have another 80 years, pushing the "crisis" up to 2116; if they had allocated even one more bit to the integer part (splitting it 33/31 vs. 32/32), we'd have another 136 years! But then light could travel a whole 14 cm before we noticed
  24. Mathwiz
    You did take note of my handle, didn't you? Hmm... that's the same point I made just a few posts ago - but was curtly shot down by.... I guess we'll just have to agree to disagree. I'm more interested in what Mozilla could have accomplished, had they stuck with UXP, or perhaps split FF into (ahem) "two distinctly different products" (say, FF Classic and FF Quantum); I guess you're more interested in things as they are now. To be fair to Mozilla, I understand that modern Seamonkey still retains a vestige of UXP support, although I haven't really followed SM much since the end of XP support. But SM isn't the product Mozilla pushes, and the SM user base is a small fraction of Mozilla's total. Exactly; that's what I was getting at. How long until we have to contend with FF 1000, even at the current rate? A very long time. But how long until there are 1000 different FF's floating around out there, when you include ESR versions and consider FF Android separately from FF Desktop? Not nearly as long. Heck, if you include Seamonkey and/or count "Nightly" releases, I think we already crossed the 1000 mark a long time ago!
  25. Mathwiz
    AIUI Mozilla is currently burning up version numbers at the ridiculous rate of 13 per year - more than 1 per month! But it'll still take them nearly 70 years to get to FF 1000. Of course, if they went to weekly updates, they'd get there in under 20. Even I might live to see that!
×
×
  • Create New...