Jump to content

DanR20

Member
 View Profile  See their activity

  • Posts

    413

  • Joined

  • Last visited

  • Days Won

    7

  • Donations

    0.00 USD 

  • Country

    United States

 Content Type 

Everything posted by DanR20

  1. DanR20
    @roytam1 The 2022-Apr-02 Serpent 55.0 version won't allow the creation of a new tab. I tried it with a new profile with the same result.
  2. DanR20
    Tried it and not working here either, would love to see that get fixed. Been using it on XP and without question despite a few bugs it's the best pre-Quantum version I've experienced. Works great on Win7 and 10 as well. There must be a reason Moonchild abandoned 55.0 for an earlier one but glad he did since it would probably have ended up with the same performance issues that PM and 52 have.
  3. DanR20
    Regarding the new version 55.0: in that weather site posted it will come in if noscript 5.1.9 options/embeddings "Forbid WebGL" is unchecked. That setting is for untrusted sites only but even when weather.com is made trusted it still fails to load. There appears to be a new interaction problem with noscript since the previous version didn't have this, at least with WebGL. https://weather.com/weather/radar/interactive/l/96f2f84af9a5f5d452eb0574d4e4d8a840c71b05e22264ebdc0056433a642c84 Except for the rendering of blank sites here and there 55.0 continues to have overall good performance.
  4. DanR20
    Hi Roy, Looks like you did a lot of work with 55.0, nice job. The good news is I've been using it for a while and it doesn't seem to have lost performance. I'm able to use it on Twitter and other troublesome sites with 52.0 without issues so far. There are some sites where I'm running into javascript not functioning properly. For example these pages are coming up blank when you click on one of the popular cities links. Works normally in 52.0. Maybe just a pref setting? https://www.legacy.com/obituaries/local The radar on this weather site won't come in or let me do a search on the top box. Not sure if it's noscript-related but the previous 55.0 wasn't a problem: https://weather.com/weather/radar/interactive/l/96f2f84af9a5f5d452eb0574d4e4d8a840c71b05e22264ebdc0056433a642c84
  5. DanR20
    Maybe roytam or someone like-minded could take an interest. It would probably entail some work and time but would keep these older versions going a little longer. That is until google forces something else "new" on everyone that requires only the most modern and up to date. IOW google chrome.
  6. DanR20
    It's too bad they can't port over recent firefox web components but they're probably missing APIs to do that. More and more sites will start going with it making these older browsers unusable eventually. There's also newer technologies coming around that require more resources and make the browser slower.
  7. DanR20
    That most likely explains it. Currently I'm only running into problems with 4 or 5 sites, including github that don't render properly with 55 so for those I use the "Open with" extension to open 52. I expect over time that number will increase.
  8. DanR20
    Does anyone know what sites this pref actually works on? It's a no go for github or gitlab. What's unfortunate is that the polyfill extension used to bring github in but not anymore. I should probably try to file an issue with JustOff and see if he might consider looking at it. Although 55 is behind 52 for me it's still overall better in performance.
  9. DanR20
    Just tested PM 30 and nothing much has changed. If you use twitter for a while or go to a hotmail account it causes performance issues and that's just the ones I know of. The scrolling on all sites and tabs starts to stick until the browser eventually becomes unresponsive and you're forced to reboot. This was with a fresh install and no addons. Interesting that roytam's 45 and 55 versions don't do this so for XP I'll continue relying on these. Until they take it seriously their browser will have limited usage since millions of people visit these sites.
  10. DanR20
    You could try locking the pref, although I don't know if it will prevent blacklisting. Change that pref to default (assuming it's 1 or whatever it is) then close the browser. You would need to create two files: config-prefs.js config.js In the config prefs.js file copy this in and place it in the basilisk\defaults\pref folder pref("general.config.obscure_value", 0); pref("general.config.filename", "config.js"); In the config.js copy this in and place it in the basilisk root folder: // lockPref("gfx.blacklist.layers.direct3d9", 1);
  11. DanR20
    That pref doesn't exist in my setup so it probably only shows if it's blacklisted?? For me it didn't make much difference changing those settings, the slowdown in performance wasn't affected. It might help others though.
  12. DanR20
    Trying both those settings: " layers.acceleration.force" and "layers.prefer-d3d9" to true. Also changed "layers.low-precision-buffer" to true. Hopefully that makes a difference.
  13. DanR20
    @VistaLover There must be something going on with my profile. I just setup a new test profile and it is coming in so I'll have to go through each addon and disable them one at a time. Edit: it was a very simple solution, uBlock was to blame so I just whitelisted github.
  14. DanR20
    How do you know if it's blocked? I've tried experimenting with different settings since some sites like Twitter have a real hard time with 52.0. Does changing "layers.prefer-d3d9" to true have any effect?
  15. DanR20
    JustOff is trying to keep up with github changes, he's just released another new polyfill version but I still can't get it to work anymore in 52.0. If anyone wants to try this site and see if it comes in let me know: https://github.com/3dyd/LAVFiltersXP
  16. DanR20
    It was a 1996 used IBM business model bought directly from them that I only paid $75.00 for 20 years ago when IE6 was still functional. I can't imagine what anyone would want with that today other than as an antique. Never even considered the idea but now wish I had, you might be right.
  17. DanR20
    OSs like 2000 hang around because they tend to work right out of the box. Not only that they install on much older hardware. I had W2k loaded years ago on a Pentium 133 with only 145mbs ram. Today you could barely render the simplest websites with that if you could even find a workable browser. Just for fun I fired it up recently and managed to get Firefox 31esr to load some sites before finally throwing it away in the dumpster. Millions of people around the world still rely on older hardware; maybe not quite as bad but not necessarily modern by current standards either so we'll be seeing third party support for w2k and even 98se for years to come yet.
  18. DanR20
    This error I can confirm in both 52 and 55. Working fine in newer FF versions.
  19. DanR20
    Thanks for that link, it works perfectly. I already had those two files created to lock in media.hardware-video-decoding.failed to false so it was real easy. Wish I knew about that hack earlier after spending several hours testing different addons to finally get one that worked. :--)
  20. DanR20
    That's a good question, I wonder if anyone out there has applied any of these recent security patches to FF 52.9.1? Really all it needs to make it as almost as useful as UXP is to add in security.tls.version.max - 4 and restore general.useragent.override. I was able to get an addon for that but the built-in option is so much easier. Also, replacing FF 52.9.1's mozavcodec.dll, mozavutil.dll, and mozglue.dll with those from 52UXP and it can use the ffvpx mp4 codec and without the need for Adobe's plugin. The good part is it doesn't have the browser performance issues that will never get fixed in PM/UXP.
  21. DanR20
    It's definitely on their end. I downloaded the latest 32-bit official Pale Moon running on Windows 10 and it's behaving exactly the same as 52 UXP. The trick is to get on a Twitter page and scroll down a while, the farther you go the worse it gets. Keyboard scrolling on other tabs begins to stick then eventually the whole browser freezes and you have to kill in Task Manager. Another way is to go to an outlook.live.com account and it happens even quicker. No such loss in browser performance with 45.0, 55.0, or FF 52.9.0. I'll try to file a bug but with Tobin it's doubtful they'll even bother with it.
  22. DanR20
    Interesting test but I can only go by my own experience. I can browse heavy sites like Twitter all day with 55 and the browser never slows down, sticks when scrolling or freezes the UI as it does in 52. It's possible that it's actually some UXP features that are causing that in 52 and porting them to 55 will carry over the same problems. Hope not because then I'd have to stay on an older version. One way to find out is to run a Firefox 52ESR profile to see how it performs then I'll know if it's UXP features or the browser itself. Update: FWIW I've been running a copied 52UXP profile using Firefox 52.9.0 and have been surfing Twitter and other sites like Hotmail that I'm having problems with in 52UXP with no loss of browser performance. There's something specific to UXP as well as New Moon 27 and 28 that are experiencing similar problems. Roy should I file a bug with the Pale Moon team?
  23. DanR20
    It's mainly about performance. 55 renders javascript better, it handles sites like Twitter better and is just faster in my experience. It is also a later version that can install certain useful addons that 52 can't such as the container tab add-on. @NotHereToPlayGames It is and can render most sites that 55 can't. That's why we want to get UXP features ported to it so it's equal to 52.
  24. DanR20
    These days I avoid updating monthly, usually it's about every 3 or 4 months so maybe that's why it takes so long to patch. I rarely use Windows 10 anyway and from what I can tell Win11 is even worse. I actually have more pleasure working in XP with older software, you could do more and it was easier. For example, the Nero version 7.7.5.1 is perfect for encoding DVD to MP4 and it doesn't install in Win7+.
  25. DanR20
    Those were the days. Windows 98SE took even less, usually around 30 minutes. Now just installing a Windows 10 cumulative patch takes at least that long. Yesterday when installing December's patch I was able to get some coffee and lunch and do other chores and when returning the installation bar was still only a quarter way. It makes me wonder exactly what Microsoft is doing to this computer.
×
×
  • Create New...