Jump to content

Mathwiz

Member
  • Posts

    1,841
  • Joined

  • Last visited

  • Days Won

    50
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Mathwiz

  1. OK, so my test plan for tomorrow is: Download and unpack @roytam1's FF 52.0.a1 build linked above Install the UOC Patch & Enforcer for FF 45 Scroll up & down in some web pages and look for the issues seen above. Try both with e10s off and on. Any suggested Web pages to try? Is MSFN enough?
  2. The name "New Moon" was built into the Pale Moon source repo as a placeholder for anyone making an unofficial build of Pale Moon. It was always recognized as a temporary name. In the original thread, I and many others made many clever suggestions for a permanent name, but none caught on, so @roytam1 just kept using the New Moon name. I'm reluctant to restart the cacophony of suggested names again. "Whistler" may not be that inspiring, but it's not bad and fits a theme. Let's get this done at last.
  3. Adobe's online installer isn't a Trojan AFAIK; it's only problem is that it doesn't work on XP. As for Avast, I'm aware of their snooping: As I hinted in the last line, sometimes that's the price of a "free" product. So they bumped the revision up to 68.9.... No idea why @caliber wants to be version 2 though; that's pretty a old FF version.... I'm still using version 60.9 on my user agent; most sites don't seem to complain about an "outdated dinosaur browser" as long as they think you're running a post-Quantum version. Must have been changed by July 19; that version reports Basilisk/20190719 In the 20190719 build, toggling it false has no effect: you still get Basilisk/20190719. But by build 20191115, toggling it false works: you get Basilisk/52.9.0. So they must have fixed it somewhere between those two points. I doubt many sites check for a "Basilisk" UA segment, but there may be a few.
  4. It is true. The online installer downloads and launches, and on Win 7 it runs fine. But on XP this happens: The offline installers at the links @Bersaglio posts work fine on XP.
  5. Online installers for Adobe Flash no longer work on Windows XP. Use the links to the offline installers posted by @Bersaglio here:
  6. Yep - mine auto-updated and I didn't even notice until I read your post.
  7. That's hopeful news for FF 51, which is on par with SM 2.48. Of course we don't have an SSE-only build of FF 51 for you to test. But I could test it on Win 7, if I knew how! If APZ/tiled compositing work in FF 51, that would narrow the search significantly for where they got broken (must've been between FF 51 and FF 52).
  8. Thanks for the heads-up; that will surely affect my browser downloader batch file and, I suspect, @i430VX's installer.
  9. Were you able to confirm that APZ and/or tiled compositing are not broken in SM 2.48?
  10. Well, I'm home for the weekend, so I decided to try on my home system (also Win 7), but discovered that here, I already had the v1.4.9 installed that has been so elusive on my Win 7 work PC.... But I'm sure you're onto something. I noticed with interest that Serpent 52 is "lying" to the Mozilla server and claiming to be FF 60. Serpent 55 claims to be FF 55 (even though it's closer to FF 53), and as you noted, it's stuck with v1.4.8.... (I suppose the proper "lie" would cause the server to download v1.4.10 , although it wouldn't work since Basilisk and Serpent don't have the required hooks yet....) The only question is, even if you migrate a profile from another browser (a practice I'm aware you're implacably opposed to, as you first made clear when I migrated my profile from Serpent 52 to 55; but my migration from FF 52 to Serpent 52 occurred long before then), defaults don't get migrated - only user set prefs do! So if it's wrong, I must have changed it manually, either back on FF 52 or an early version of Serpent 52. But why on Earth would I have ever modified that obscure pref? So I went searching, and am rather sure I found the answer. The following is in a "spoiler" at the Adobe Primetime thread: Thanks go to @mixit for keeping those obsolete instructions for "historical" reasons! Turns out Primetime works on both FF 45 and FF 52, but neither of those versions supported it officially, so to get the server to download it, you had to "lie" and tell the server you were running the closest supported FF version! That "lie" is no longer needed or useful with Primetime, but it would have the side effect of downloading Widevine v1.4.8. So I'm sure when I get back to work Monday, I'll find that pref user set to spoof FF 51 vs. the default of 60.
  11. Yes, that color is much more readable; thanks! Actually I have v.1.3.0; at one time I tried v1.4.0 but IIRC it didn't work correctly, so I rolled back to v1.3.0 and it worked fine.
  12. You're not going to believe this - it downloaded and installed 1.4.8.903 again! This was with Serpent 52.9.2019.11.15 (last one before Primetime stopped working) on Win 7, with Firefox & Gecko compatibility enabled. I tried again, but this time, before I went to the Axinom site, I checked about:addons#plugins. It said "Widevine Content Decryption Module provided by Google Inc. will be installed shortly." It remained in that state until I visited the Axinom site, at which point I got a notice at the top of the screen: "Serpent is installing components needed to play the audio or video on this page. Please try again later." Then it installed 1.4.8.903 yet again. I suppose official Basilisk might fare better (although "better" in this context would be v1.4.9.1088, which still wouldn't play squat). It's probably something we'll need to figure out if/when official Basilisk catches up with Google's ever-changing DRM requirements.
  13. Sorry for the delay; it's been a busy week. I can understand MCP removing Primetime support, since the Windows versions they support have WMF and thus don't need it the way XP users do. I can confirm that under Win 7, Primetime works on Serpent 52.9.2019.11.15 (with media.ffvpx.enabled & media.wmf.enabled both set to false) just as it does under Win XP. And Widevine is visible, although I still have v1.4.8.903 for some reason. (See attached thumbnail.) Unsure why it never updated to v1.4.9. Not sure it matters now, since one needs 1.4.10 now and AIUI 1.4.10 isn't yet compatible with Serpent/Basilisk. I'll recheck with 52.9.2019.11.22 tonight, but I expect you're right: Primetime and Widevine will still be visible but Primetime won't work. IIRC @dencorso originally installed Primetime because the built-in support (media.ffvpx.enabled) produced distorted audio on some sites. I asked about this issue not long ago, but Serpent users were getting around it by just setting the Firefox compatibility settings in about:config (apparently some web sites use an audio codec Serpent/Firefox can't handle if they don't see Gecko/Firefox in the UA). BTW, thanks for the "FT-DeepDark" theme link! Only problem I see is that the "Tab Tally" drop-down menu has very low contrast with it. Know of a way to fix that annoyance?
  14. Placeholder (reserved for use further on).
  15. Guys, how hard can you make this? Facebook will nag you if it sees you're running FF 45. I recommend going into about:config, creating a new string preference called general.useragent.override.facebook.com, and setting it to Mozilla/5.0 (Windows NT 6.1; WOW64; rv:57.0) Gecko/20100101 Firefox/57.0. @roytam1's FF 45 builds support SSUAOs of this kind, so this will tell Facebook you're running FF 57 on Win 7, and it won't nag you anymore. No need to install any browser add-ons. Please don't do this! It's not required and will only disable the above setting, ensuring you get nagged by FB to update your browser. As explained earlier, FF 45 doesn't have built-in support for h.264 video. You need to add something.... Since those browsers run on your PC, you have an sse2 processor; therefore, you could install the Adobe Primetime CDM using the instructions at the first post of @mixit's thread. I've confirmed that Primetime works with @roytam1's FF 45 builds. However, most FF 45 users probably don't have sse2 processors. Those users should instead download the @roytam1 LAV filters for their architecture (links are in the first post of his original thread), and unpack them into the same folder as firefox.exe. Either method will let FF 45 play videos. I believe other possible methods (e.g., Flash, Silverlight) are no longer supported by FB, but I may be wrong about that.
  16. I'm sorry too; profiles.ini does exist in my Serpent 55 installation: You do need to create a second profile in order for changing the setting to 0 to work, though.
  17. Slight mistake in that first quote: profiles.ini is 2 levels higher, in folder containing "profiles" folder, not in profiles folder itself.
  18. Unfortunately no; I jumped from XP over Vista to 7. But I know there are several Vista users here, including ...
  19. You may be right - you usually are - but ... ... so I think it's at least worth a try.
  20. ... which is why I added You need to install the Adobe Primetime CDM.
  21. I'm sure Mozilla had (what they thought was) a good reason to redo the rendering engine in FF 49. It's probably tied into a thousand other things. So I'd expect putting the old engine into a new browser to be a bit like transplanting a brain.... I imagine there's some way to fix it; I just don't think that's the right approach. @VistaLover's probably our best expert on these questions, though, so I'll defer....
  22. OK, so the e10s code is still there; it just doesn't work properly in the SSE-only build. Weird, but it is what it is, I guess. Wouldn't the NM28 version of the patch be your best bet, since the only difference between the 52 version and the NM28 version was the latter not enabling e10s? Yes, I would generally expect it to behave the same as the SSE2 build; bugs and all, unfortunately. Fixing it is certainly possible, but probably not a trivial task. There were many changes between FF 48 and FF 49, AIUI. @roytam1 would have to figure out which one(s) broke APZ and tiled compositing; then perhaps they could be reverted, but it depends on whether later changes depend on the ones needing reversion.
  23. Heck - just making Chrome 76 Vista-compatible would help some of us! (But please keep striving for XP compatibility.)
  24. Try findstr; e.g., findstr /rxv "\[.*\]" "<infile>" >"<outfile>" I believe that will filter out any lines that start with a "[" and end with a "]".
  25. Interesting, since the regular (SSE2) build does support E10S. Not a big deal, but curious: did @roytam1 have to remove the e10s code to make his SSE build work?
×
×
  • Create New...