Jump to content

Mathwiz

Member
 View Profile  See their activity

  • Posts

    1,728

  • Joined

  • Last visited

  • Days Won

    49

  • Donations

    0.00 USD 

  • Country

    United States

 Content Type 

Everything posted by Mathwiz

  1. Mathwiz
    I liked yours better!
  2. Mathwiz
    Yes I do, but I never needed service workers for MSFN before Again, yes I do, but those prefs exist in the 2023.08.25 version too. So I will test these suggestions, but even if enabling service workers and/or animations works around the problem, what changed between 2023.08.25 and 2023.09.01 that caused this problem to surface? Edit: layout.css.animation.enabled was the one. Enabling service workers and/or layout.css.transition.enabled had no effect. I still want to know why it's necessary in the current St 55 version but not the previous one. Edit 2: OK, I must be losing my mind! In the 2023.09.01 changelog, there's this entry: - Issue #2293 - Add preferences to disable CSS animation/transition props. (f4cc47c049) ... but I know those prefs appeared in the 2023.08.25 version and they worked in terms of stopping the CPU-hogging animations we were all up in arms about a couple of weeks ago, but didn't break MSFN: I tested them myself! Nothing makes any sense any more.
  3. Mathwiz
    @roytam1: newest (9/1) version of St 55 has an annoying problem on MSFN: pop-up windows won't go away. Examples: Click the + sign on any post. A pop-up with a button reading "Quote 1 post" appears. Click that button: the pop-up remains on screen but the text changes to "Quote 0 posts." Click the number next to a "liked" post to see who "liked" it. A pop-up appears listing the "likers." Click the X to close it: it doesn't close. You must refresh to remove the pop-up. On the topics list page, hover over a topic. A pop-up appears showing the first post. Move the mouse: the pop-up doesn't fade away. Again, you must refresh the page to remove it. The 8/25 version of St 55 works correctly in these cases, so I'll be sticking with the 8/25 version for now.
  4. Mathwiz
    Folks, be nice. The author clearly isn't a professional Web developer, and for that we should be grateful! A Web site can still be useful without all that "flash" and "sizzle" and the CPU/GPU-sucking CSS and JavaScript that goes along with it. (I agree with NHTPG about the ridiculous anti-Wikipedia rant, though.)
  5. Mathwiz
    Don't know of any (other than test Web sites) myself, but HEVC is the video compression algorithm used by ATSC 3.0 (an over-the-air TV standard used in North America and South Korea). So it's a good bet HEVC will be coming to the Web soon as well. So HEVC support in UXP isn't an urgent need, but wouldn't it be good to get ahead of an upcoming standard for a change, instead of waiting for folks to start complaining that they can't watch videos on some Web site?
  6. Mathwiz
    Probably not very useful, but better than a 404: St 55 goes to https://addons.mozilla.org/en-US/firefox/collections/4757633/webdeveloper/ which is still active. I'm sure St 52 could be changed to point there - or to get the URL from a pref and default the pref to the above URL.
  7. Mathwiz
    Do you know how much the last computer I bought cost me? $10.41 in 2020. It was a Raspberry Pi 3B+. Heck, the cost of a keyboard, monitor and mouse (especially the monitor) would dwarf the cost of the computer itself. It was so cheap I "splurged" and got a case for it for another $11. Sure, it doesn't run Windows - it runs (free) Linux - but it's amazingly powerful! So I really think the cost of new hardware is a complete red herring. The real reason folks stick with their "favorite" Windows, be it 7, Vista, XP, or even 2000, is that M$ has made it a royal PITA to "upgrade." First, you usually need a new PC. You might be able to upgrade one time "in place," say, from Windows 7 to 8, but why would you want to? And to go from 7 to 10, you're probably gonna need a new PC. Then, how do you get all your apps and everything off your old PC and onto your new one? Gone are the 9x days when you could just pull the HDD out of the old PC. plunk it into the new one, and install the new Windows version. In fact, in all likelihood, the new PC won't even run the old Windows version! No, instead you need to buy special software to move everything over - and even then, it usually fails on at least a few of your apps. And even if you get all that done successfully, M$ always manages to screw up something that was working fine in the previous Windows version. Did anyone really like the "Metro" UI that came with Win 8? Heck, you can make Win 7 look just like Win 98 if you want, so why did M$ forget that lesson and make that Metro monstrosity mandatory on Win 8? And with Win 10/11, it's the same story: you're gonna get the new UI whether you like it or not. Not to mention M$ dropping WMC with Win 10 (yes, I'm aware there's an unofficial way to keep it during an upgrade). To be blunt, if you're gonna "upgrade" to Win 10/11, you ought to at least consider a Mac or Linux. Both offer a Windows environment that's probably as easy to port your apps to as the latest/"greatest" Windows.
  8. Mathwiz
    I tried 360EE and sure enough, the HEVC clips do play, but I have an older APU without built-in HEVC decoding, so the video playback is unsatisfactorily choppy. So even if it worked in UXP, you'd probably need a reasonably up-to-date graphics card for it to be worthwhile. OT: I suspect that's a deal-breaker for ATSC 3.0 on this old PC, unless I buy a new graphics card for it. (And the card would need Win 7 drivers, so it couldn't be too new....)
  9. Mathwiz
    (Showing my ignorance here.) I would naively think that on Vista+, WMF would support HEVC. (I suppose you'd have to install a codec for it first.) But evidently there's more to it than that. Wouldn't help XP users anyway.
  10. Mathwiz
    https://tools.woolyss.com/html5-audio-video-tester/?u=woolyss.com/f/caminandes-2-gran-dillama-x65-aac.mp4 https://tools.woolyss.com/html5-audio-video-tester/?u=woolyss.com/f/caminandes-3-llamigos-x265-aac.mp4
  11. Mathwiz
    As I also reported in @roytam1's browser thread, for the second time this year Chase.com has upped their minimum required browser version. The first time, they raised it to Chrome 95, but our browsers based on Chromium 86/87 still work as long as you override the user agent. Now, they're raising it again. A trial-and-error search indicates the new requirement will be Chrome 109. That cuts out my old Android 6 phone, which topped out at Chrome 106. But they haven't done it yet (it's just a warning at this point), so I can't yet say whether our browsers will fail or work if we override the user agent.
  12. Mathwiz
    Is that on your "loved" St55 ? Because St52 (2023-07-31) (32-bit) has below SSUAO: general.useragent.override.chase.com;Mozilla/5.0 (%OS_SLICE% rv:112.0) Gecko/20100101 Firefox/112.0 I don't think it's a 52 v. 55 thing; it's just a matter of how obsessively you install @roytam1's weekly updates. The Aug. 18 version of St 55 spoofs FF 102, but surprisingly the July 28 version specified FF 112. Both work, but produce a warning, on the current Chase site. Edit: I see you discovered the same weirdness in St 52 almost a week ago. So far, so good; but I don't expect that situation to continue for long. From the linked PM article: Actually, from the examples the poster gave, I don't think that's the whole story, since she reported: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Goanna/6.2 Firefox/102.0 PaleMoo/32.2.0 did not work, while Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Goanna/6.2 Firefox/102.0 PaleMoo32.2.0 did work. The only difference was the slash between "PaleMoo" and "32.2.0," so it's not at all clear to me what Chase is doing.
  13. Mathwiz
    Noticed a couple of things there: first, But later: So I guess you were one of the "lucky" ones that got "selected" well before the end of 2023. Second, here's the excuse they gave: I don't think for a minute that Micro$oft cares one bit about "protecting developers." If that were the case, they could've made this optional, perhaps with a banner on your page so visitors would know whether you'd enabled 2FA. No, I think this has to be about protecting Micro$oft. I think they're worried that someone will upload bad software (buggy, or conceivably even malware) to GitHub, the guilty party will claim that their account was hacked, and Micro$oft will get sued for lax security. Making 2FA mandatory is intended to remove the "my account was hacked" excuse. Which, I suppose, is fine; if that's what they feel they have to do to protect themselves from legal liability, so be it. I just wish they'd drop the "we're trying to protect you" malarkey. Third, I see they do support 2FA via SMS, but.... I don't know why it doesn't provide "the same level" of protection, but that makes me worry that other sites requiring 2FA will soon stop supporting SMS as well, so even non-GitHub users may soon find themselves in the same boat. So thank you for the advice on KeePass. XP/Vista users may soon need it, GitHub or no GitHub! Seriously? I couldn't possibly care less how Mozilla prefers I abbreviate the name of their product. It's clear what "FF" means in context! But at least they didn't suggest "F5x"....
  14. Mathwiz
    Well, that didn't last long! Built-in SSUAO pretends to be FF 102; guess that's no longer good enough! Edit: FF 113 is the minimum to avoid the warning, but I wonder what new Googlisms (or conceivably Mozilla-isms, but I'm still betting on the former) will be needed in order to access chase.com, once "soon" arrives?
  15. Mathwiz
    Well, there's 2FA, and there's intentionally annoying 2FA. Only form of 2FA I've ever used is the kind where you log in and they send you a OTP, via either text (so you need the cell phone it gets sent to - doesn't have to be a smart phone though) or email (so you need to prove you have access to your email account). Those aren't too bad, and a lot of sites will set a browser cookie so you don't have to do it again, at least for a while. No "special app" needed! But from what you're saying, it sounds like GitHub will require a special app just to generate the OTP. I can't see any reason for such a requirement, other than to discourage folks from logging into GitHub unless they have to! 30 seconds to key the darn thing in sounds awfully tight too. (That may be the reason you need a special app - text or email would often take longer than that.) GitHub isn't a banking or financial site - or even your email account! Why are they doing this?
  16. Mathwiz
    New animation pref works like a charm. When set to false: ... and CPU usage is sane again.
  17. Mathwiz
    We seem to have drifted a bit off topic with all this discussion about who's a "real" XP user. If you need a browser that runs on XP, you're welcome here, regardless of how "real" your XP use may seem to others. Thanks for the clarification, although I'm surprised that anything on bugzilla is still relevant to UXP! (Considering how much FF has diverged from UXP in the last several years.) Thank you! A couple of simple prefs make a lot more sense than jumping through hoops to get the necessary code off userstyles.org! (Seriously - they actually look for the word "Chrome" in the browser user agent? Sounds to me like a good reason to avoid them altogether!)
  18. Mathwiz
    Maybe this has been going on for a while, but I just now noticed the links: Is MCP using BugZilla to track UXP bugs now?
  19. Mathwiz
    You're probably right, but Serpent gobbles CPU on that page even under Win 7. I should say that I don't know enough about GPU programming to know what it would take to bring down the CPU usage on an XP- (or even a Vista-) compatible browser. Even if it's possible, though, it's probably not worth doing since it's so easy to just kill these animations.
  20. Mathwiz
    I see it. It's sort of like clouds or smoke or the like slowly drifting left over a grey background. (But if you scroll down the page too far, it goes away.) Serpent uses 37-38% of my CPU (an old 2-core AMD A4) when I switch to the tab with that page. That seems like an awful lot for a purely cosmetic effect. I'm guessing the more modern browsers use the computer's GPU vs. its CPU for this effect. While that's a drawback of our browsers, the page is fully functional without the animation, so I'd say just kill it as @Ben Markson suggested.
  21. Mathwiz
    Oh, come on. You cannot even enable e10s in New Moon. But you can enable it in Serpent (both 52 and 55). Did you try that? If not, you did an "apples to oranges" comparison: FF with e10s is faster than Serpent without e10s. Well, duh; FF with e10s is faster than FF without e10s too - that's why we have a whole thread on enabling it! (To be fair, FF/Serpent with e10s is quite the memory hog - and still slow - compared to Chrome 86/87 ports. So I wouldn't recommend it unless you've beefed up the RAM in your PC, preferably with 64-bit XP or later so you can get more than 4GB, or at least with an SSD for the swap file.) Technically, you're right about that. Multiprocessing is mostly a convenience for developers. But that said, it does have its advantages for us end users. Beyond the obvious (letting a 32-bit app use more RAM), if your tab crashes in FF/Serpent, and you're running in the default single-process mode, your whole browser crashes! But if that happens in multiprocess mode, you just reload the tab. <rant> And why shouldn't she be? The original idea behind HTML was supposed to be that any browser, no matter how primitive, would render a "usable" Web page, merely ignoring the tags it didn't understand. If you use a browser from 2001, it may look like a Web site from 2001, but you're still supposed to be able to use it, at least. But that's long gone, thanks largely to Google (but also others including Mozilla). Nowadays, if your browser doesn't understand the latest bullish snarkifying operator added to JavaScript in the latest Chromium release, you're likely to just get a totally blank page (or if you're "lucky," a curt message telling you to "upgrade" your browser, even if that means "upgrading" your OS to the latest monstrosity from Micro$oft, and in turn buying a new PC capable of running that monstrosity) because the Web designer used JavaScript with that bullish snarkifying operator to build the entire Web page from scratch! HTML? Who needs it? (With the side effect being you can't disable JavaScript any more, and have to rely on other, more complex means to block the spyware embedded within.) So yeah, we're angry. Not (for the most part) because we intend to use a PC that old, but because we shouldn't have to keep buying newer, more expensive PCs every few years just to keep doing the same exact things we've always done, just because some Web framework developer couldn't resist using that shiny new bullish snarkifying operator (for "security")! </rant>
  22. Mathwiz
    Well, it could be, yes. I'm just going on past experience: so far, Google has been behind far more UXP-breaking changes than Mozilla, so I figured the odds are pretty good that the next one will be Google again. (And my usual disclaimer: Not all UXP-breaking changes are "egregious;" i.e., serving little purpose other than to break older browsers. Some are quite useful to Web designers. Many do strike me as quite egregious, but I don't know enough about all this new CSS stuff to have an informed opinion yet.)
  23. Mathwiz
    So until MCP implements the "revert" CSS feature, the "best" workaround is far from ideal: toggling pref layout.css.is-where-pseudo.enabled to false, thus restoring the CSS behavior of previous UXP browser versions. Of course, by the time MCP does implement "revert," it's nearly certain Google will have come up with something else, and MCP will have to run even faster to stay in the same place.
  24. Mathwiz
    A little bold text would probably help: "New New Moon 27 Build!" Otherwise it does look kind of silly. For the beginner, I'd recommend starting with New Moon 28. If you find NM28 impossibly slow on your PC, try New Moon 27; it's less resource-intensive, but it's based on an older Firefox version so it won't work with as many Web sites.
  25. Mathwiz
    *sigh* More "features" to implement. The Red Queen's race continues....
×
×
  • Create New...