Jump to content

Mathwiz

Member
  • Posts

    1,867
  • Joined

  • Last visited

  • Days Won

    51
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Mathwiz

  1. Thanks @looking4awayout! The FF 45 prefs should work with newer forks (NM 28/Serpent), although those require SSE2 and are thus probably running on faster processors so you may not notice as much difference in performance. Folks, if you already have prefs set that you don't want to lose/reenter manually, you'll have to merge his prefs.js files with yours thusly: Open your browser's profile folder (go to about:profiles and on the active profile, click "Open Folder") Close your browser. Open @looking4awayout's prefs.js in a text editor such as notepad. Select all the prefs and copy them to the clipboard. Open the prefs.js in your browser's profile folder in a text editor. Paste in the copied prefs right after the comments at the beginning of the file. Save the merged prefs.js file. Reopen your browser. If there are any duplicate/conflicting prefs, your settings should take priority; everything else will come from @looking4awayout's file. Next time you close your browser, prefs.js will be rewritten with all prefs in order.
  2. According to the wiki, the add-on provides some improvements over the support built into FF 52 and Serpent. Unfortunately, I just tested version 4.0.2 of Multi-Account Containers, and my experience matched @DanR20's: So it looks like 4.0.2 installs but doesn't run correctly, whether or not the built-in support is present. Same result in Serpent and FF 52.9.1. I'll try some older versions and report back. Edit: I tried several versions all the way back to 2.3.0. They all do the same thing as 4.0.2. Edit 2: v4.0.2 of the add-on works in Serpent/Moebius! In fact versions up through 4.1.0 are compatible with Moebius. BTW, the add-on does make containers quite a bit easier to use. To open a new container tab, you don't have to go to the File menu; when clicking the "new tab" (+) button just hold the mouse button down for a second or two, and the "new container tab" menu will appear. Also you can right-click on a Web page and click "Firefox Multi-Account Containers / Always Open in This Container" to "pin" the current site to the current container. Then, any time you click a bookmark or link for that site, you get asked whether to open the link in the current container or in the "pinned" container for that Web site. Edit 3: You can enable the new container menu from the new tab (+) button without the add-on, so it can be used in Serpent/UXP. Just create a new integer pref named privacy.userContext.longPressBehavior and set it to 2. Other add-ons that change the behavior of the new tab button may keep this from working, though
  3. FF 60 ESR actually isn't bad - I have a copy on my Win 7 PC - but It doesn't run on XP/Vista and cannot be made to do so It doesn't support NPAPI plug-ins, nor does it offer a substitute like PPAPI; say goodbye to Java, Silverlight, etc. It doesn't support any pre-WE add-ons Last (and TBH, least) it sports a new UI, which wouldn't be bad if it didn't look so much like Win 10 Basically, it's a brand-new browser that happens to be somewhat compatible with your old FF profiles. About the only thing it has in common with FF 52 ESR is the name (and a few WE add-ons).
  4. I'm still trying out containers. I've found it useful for logging into both my and my wife's bank account at once, without having to go to about:profiles, set up a second profile, install all my add-ons and custom prefs, etc. And the color-coding helps me keep track of which tab is for which person. That's about it so far, but remember - I only learned of it because MCP stripped it out and drew out the one person on this thread who uses it! I'd encourage others who find the containers concept intriguing to download the 3/23 version of NM or Serpent, toggle on the prefs, and give them a try. To be fair, perhaps you should also try the 3/30 version and see if you notice better performance opening tabs, etc. with the feature removed. The feature could use improvement. I'd like to see a way to associate a bookmark with a container, so you just click, say, the Amazon bookmark, and Amazon opens up in a new "shopping" container tab. That would save key/mouse strokes vs. opening the container first, then opening the bookmark. Perhaps MultiFox will mature someday, and the built-in support for containers can then be removed. BTW, I also installed the private tabs extension. A private tab is sort of a "throwaway" container tab: open one and you have a new container; close it and the container is gone for good, including any cookies or unexpected NSFW content (although I'd probably flush my cache anyhow just to be sure). Excellent option for the first visit to a site you aren't sure you can trust. Opera 12 had private tabs and I've missed the feature in Firefox and Serpent. The latter have private windows but those aren't as convenient.
  5. The nice thing about open-source software is that nothing ever goes away completely. Moebius may have been a dead end for PaleMoon but it's still a useful and (with TenFourFox's and @roytam1's help) secure browser. In some ways it's the most advanced browser available for Windows XP and Vista. I use Serpent/UXP vs. Serpent/Moebius because it has better compatibility with FF 52 ESR, and it benefits from MCP's current development efforts, but I understand why some folks choose Moebius (especially since MCP's understanding of "development" occasionally means removing useful browser functionality).
  6. I think that's actually the default (well, except for the Win 7 part) if you don't turn on FF compatibility; if you do turn on FF compatibility, you get a "mixed" user agent string by default that includes both Firefox and Palemoon/Basilisk. (By default the FF part of the string claims 60.9, at least with Basilisk/Serpent.) I don't trust that default, though; I use a "pure" Win 7, FF 60.9 user agent string as my default. That does cause a few problems with other sites, such as Instagram; most of those sites then get SSUAOs to Win 7, FF 52.9.
  7. The "new feature" is that it won't work unless you're using (or can fool GitHub into thinking you're using) the latest "greatest" browser to access their site. That may not seem like much of a "feature" to you or me, but it's definitely a "feature" to GitHub's owner, Micro$oft: it sells Windows updates since those browsers won't run on Vista or earlier Windows versions. I'd guess that GitHub sends every browser (except a few specific ones) JavaScript based on the ECMAScript 2018 standard, which won't work on anything but the newest browsers. Luckily, if you pretend to be 60.x, that's one of the few browsers that will get "legacy" JS based on ECMAScript 2017 which NM 27 still can't completely handle ... I've been wondering about that myself. I would assume MCP will try either to backport the necessary JS enhancements or to update the JS engine themselves, but one wonders how practical that will be - and there's some chance they'll have to throw in the towel on UXP, and PM 29 will be Quantum-based....
  8. I guess the question on everyone's mind now is, are FF 52.9 / Serpent / New Moon / @roytam1's K-Meleon builds broken too? Is there a test page?
  9. To be fair, they did this in part for speed: ... but I suspect they were a bit overconfident in the Multifox add-on when they made this decision: Key word being "likely." If someone had bothered to test MultiFox, they might have realized it's not quite ready to replace what was removed. This isn't the first time that MCP has gotten overzealous (IMO) in removing useful functionality. It wasn't all that long ago that they removed all WE APIs, thus forcing most users to either dump all their WE add-ons (with Basilisk) or all their legacy add-ons (with Firefox). Luckily for us @roytam1 reverted that change in Serpent. This time, it looks like Matt A. Tobin was on the side of keeping the functionality, at least in Basilisk: The big difference this time is that fewer folks knew container tabs even existed. I didn't know about them either until you mentioned them and the about:config prefs that enable them, but now that I see what they do, I can see their utility and am also reluctant to update.
  10. Depends on the version: PM/NM 28 was forked from Fx52 ESR.
  11. No, although some (many?) add-ons will work on both. New Moon, and (official) Pale Moon and Basilisk only support legacy add-ons. FF52 and Serpent support some WebExtension add-ons as well. Also, New Moon and Pale Moon have a different UI than FF52/Basilisk/Serpent, so add-ons that modify the UI may be specific to one set or the other. You can disable Serpent's built-in support under about:config. Search for media.ffvpx.enabled and set it to false. Then you can install and use the Primetime plugin using the instructions at that thread. Try this. Go to about:config, search for .azure and two prefs will show up: gfx.canvas.azure.backends and gfx.content.azure.backends. The default for both is direct2d1.1,skia,cairo. Try changing both to direct2d1.1,cairo,skia and see if that helps. There's probably no perfect solution, but one more about:config tweak may help: Try setting browser.tabs.remote.force-enable to true and restart Serpent. That enables multiprocess mode (you will see two basilisk.exe processes in Task Manager), so it will be a while longer before either process grows too big. This is incompatible with some legacy add-ons, such as Classic Add-Ons Archive, so use at your own risk. (BTW, @VistaLover discovered a way to patch CAA so that it will work in multiprocess mode, sort of.)
  12. Yours is almost the newest. @roytam1 creates a new version every week, so there is one newer version. You probably don't need to update every week, but if you insist, try this: Go to Roytam1's blog: https://rtfreesoft.blogspot.com/ Press Ctrl-F to find a string. The brower's string search box will appear Type -sse in the search box That will take you straight to the link to the newest SSE version.
  13. After next month, there probably won't be much point. Once we have the final POSReady '09 updates, someone can create an "unofficial SP5" containing unofficial SP4 plus all the POSReady updates (except any found to be defective). That will be pretty much it for XP updates (unless there's a major malware attack and M$ decides to make a rare exception, as they did with WannaCry).
  14. Yes, and depressingly typical for M$ these days. "What? You're only using Windows 8.1? You haven't "upgraded" to our latest/greatest spyware OS version? Well, a bas with you then!"
  15. I bet GitHub actually works on "real" FF 64. They probably send the FF64-compatible JS to any FF browser except 60.x and maybe a few other recent versions in that range. FF 52, NM, & Serpent can't use the FF 64 code, but if the browser is "too old" for GitHub's taste, it just sends the FF 64 code anyway (along with the out-of-date browser banner). So you have to use a spoof that's "old enough," but not "too old"
  16. I go back & forth on what "global" spoof to use. Right now I've gone to spoofing FF 60.9 globally, but with a number of SSUAO's for sites (like Instagram) that send JS that's too new if you claim to be 60.9.
  17. I suspect @glnz may have exaggerated a bit for comic effect
  18. I agree. The only thing the spoof should do is remove the "unsupported browser" warning banner. It shouldn't fix the "branches" drop-down, yet somehow it does.... It's either a bug or a deliberate attempt to frustrate users of older browsers, by sending them faulty JavaScript!
  19. The site seems to work correctly with Flash disabled. If disabling Flash doesn't help try it on Win 7. Could be an XP incompatibility within whatever plug-in is involved (surely it doesn't use Java?)
  20. Thanks. On reading that, though, I have to wonder what the heck Mozilla was thinking: So they didn't remove the UAO module (obviously, because it can be made to work), but it was slowing down page loads (has anyone here even noticed?). Wouldn't the logical fix be simply to change the site-specific-overrides pref to default to false, instead of making us write JavaScript to turn the bloody thing back on? Oh, well, be that as it may, thanks to @dickvl, @morat, and of course @VistaLover for coming up with a fix. @Dave-H's extension may still be useful in some situations, such as when you need a UAO for a specific page, rather than for an entire site, but this should cover most cases.
  21. It's probably not that sophisticated. Most likely they're using JavaScript and/or CSS features (most likely JS, since it tells you it doesn't work; with bad CSS, it just wouldn't work, a la those Instagram videos) that aren't supported on older versions of FF. Even PM/NM/Basilisk/Serpent probably haven't caught up yet (but it wouldn't hurt to try). Edit: Looks like @VistaLover inadvertently confirmed my guess: If it works on Basilisk on Win 7, but not on Serpent on Win XP, despite a UA override, then I'd start to worry.
  22. Encrypted Media Extensions? On PM/NM? I thought MCP had a law against those I suspect Widevine is nonetheless useless on XP, but I'm curious whether it now works on Vista with this update.
  23. Good question. I tried site-specific overrides in about:config, a la New Moon/Serpent, with FF 52.9.1, but they didn't work for me, even though the general.useragent.site_specific_overrides about:config preference is present and set to "true." If there's some other preference or method required to make site-specific overrides work, please let us all in on the secret! Once I installed the extension @Dave-H mentioned, I was able to do site-specific overrides via the extension's config page.
  24. One note about Serpent, which I too use on Win 7. Serpent actually supports more extensions than the Basilisk browser from which it was derived. The Web site below.... ... only lists extensions compatible with Basilisk, which use the "legacy" (pre-WebExtensions) API. You can also check addons.mozilla.org for add-ons compatible with Firefox 52 ESR that use the WebExtensions API; these add-ons will also work with Serpent.
×
×
  • Create New...