Jump to content

VistaLover

Member
  • Posts

    2,084
  • Joined

  • Last visited

  • Days Won

    93
  • Donations

    0.00 USD 
  • Country

    Greece

VistaLover last won the day on June 14 2023

VistaLover had the most liked content!

About VistaLover

Profile Information

  • OS
    Vista Home Premium x86

Recent Profile Visitors

30,070 profile views

VistaLover's Achievements

2.7k

Reputation

  1. ... Well, all I can tell you is that "my inner circle" most probably doesn't know what FUD means ; I have picked that up some years ago, by reading posts on the net ; and yes, I had to first look up its proper meaning ...
  2. ... Respectfully, "there" is off-topic , "here" it is NOT ... Actually, I did read chermany4ever's comment in the "roytam1 browsers" thread and specifically elected to respond to him inside the "proper" Supermium thread here, rather than there; and when I changed tab focus to this thread (to finish my reply), your "comment" there wasn't yet public/visible ; hence, I "continued on my merry way" ... Regards ...
  3. GitHub member Okmeque1 has recently reported that the very latest Hotfix (R2) release, https://github.com/win32ss/supermium/releases/tag/v122-hf is able to launch and run successfully in his machine; it has WinXP SP2 x86 as the OS : https://github.com/win32ss/supermium/issues/341#issuecomment-1984464451 https://github.com/win32ss/supermium/issues/341#issuecomment-1987143081 Full thread here ; you may then want to give it a try yourself ...
  4. ... I did some further testing today and it appears that the cut-off value has been set at Chrome/100.0 (for the tests to work, one has to wipe out browser cache and "sciencedirect.com"-set cookies before testing a different "Chrome/*" value ); 100+ will load the site fine in 360EEv13.x/KMB , 99- will redirect to the "browser-out-of-date" page ; since this is a block purely based on UA-sniffin', I would argue they had blocked older clients for "security-related FUD"; I don't believe their servers risk any harm by allowing those older clients though, the tactics smell of forcing the user to switch to a more "secure" browser version (however, v100 is still far from v122 , the current Google Chrome) ...
  5. ... It's probably this one : https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/getTransform Requires Fx70+ , Ch68+ ...
  6. ... Erh , you mean "previous" month ... ... That's probably true , but the other-way-round isn't a given; not the whole of UXP has been backported to St55 (but. at the same time, St55 has some vestiges inherited from Fx53.0a1); please also try, if you will, 2.16-"legacy" on UXP (probably won't work there, too, but...) ...
  7. ... Is it the "standard" or the "legacy" dist(ribution) for current UXP?
  8. ... There exist several "caches" in Chromium-based browsers: Browser Cache, App Cache, ShaderCache, GrShaderCache, Code Cache, GPUCache (this list from my KMB profile; Ch87-based ); I'm not aware of a "method" to clear browser cache on a "per-site" basis (probably exists, just not aware of it ) ... As for the second part of your question, it seems to be a recurring one : https://msfn.org/board/topic/182304-extreme-explorer-360-chromium-78-86-general-discussion/?do=findComment&comment=1216282 ... and an answer from "yours, truly": https://msfn.org/board/topic/182304-extreme-explorer-360-chromium-78-86-general-discussion/?do=findComment&comment=1216289 Then again: https://msfn.org/board/topic/182993-360-extreme-explorer-arcticfoxie-versions/?do=findComment&comment=1223512 ... and an answer from NHTPG: https://msfn.org/board/topic/182993-360-extreme-explorer-arcticfoxie-versions/?do=findComment&comment=1223515 For your convenience , it might be best to use the Bookmarks feature on your browser ... Cheers ...
  9. ... Apologies for asking, but your statement isn't quite clear to me ... SumatraPDF is a standalone application that can handle (local) PDF files, how can it be used "with" Serpent 52's native (built-in) PDF viewer (pdf.js, written in Javascript) ? Do you actually mean that for PDF files on your system, you sometimes use SumatraPDF and other times you use St52 (as a PDF viewer) ? FWIW, SumatraPDF used to come with a NPAPI plugin that could be configured to handle PDF files inside a supported browser (St52 is one ), but that NPAPI plugin was removed, starting with SumatraPDF-3.0 ; apparently, there's a hacky way to keep using the last available plugin version (2.5.2) with newer versions of the SumatraPDF application, but this is an unsupported configuration, i.e. "you're on your own": https://web.archive.org/web/20170424012056/https://github.com/sumatrapdfreader/sumatrapdf/wiki/Browser-plugin
  10. The initial implementation has issues correctly displaying emojis under Windows XP, e.g. on GitHub: https://github.com/win32ss/supermium/issues/333 A hack-y "fix" has been made available by the author: https://github.com/win32ss/supermium/issues/333#issuecomment-1982403569 (will ONLY render monochrome emojis in Win<8.1 )
  11. There exists a project (now, seemingly, an "abandonware" ), last updated in June 2020, which offers "pdf.js" in the form of a "legacy" XUL extension: https://github.com/IsaacSchemm/pdf.js-seamonkey/releases/tag/v2.3.235 The release notes of the last version state that it's based on pdf.js-v2.3.200, so you got further than them ; the provided XPI file comes with l10n support , which was the main reason I had tested it back then in my "dirty" St52 profile ; after some days of testing, I bumped on some incompatibilities (the details of which evade me now ), so I ended up uninstalling it and reverting to the St52-embedded (English-only) "native pdf.js viewer" ...
  12. (redacted) InitializeProcThreadAttributeList requires Vista SP2 as "minimum supported client" ... This crashpad crash under Windows XP has been fixed, for now in source code, only: https://github.com/win32ss/supermium/commit/08170feefcfbcd750b377d4c11a4efc67279ed9e No binary fix available yet; the next "hotfix" release should incorporate it, hopefully ..
  13. Given that the current Google Chrome "stable" release is at v122.0 as I type this, it comes as no real surprise that sites are starting to "blacklist" our "legacy" Chromium browsers (360EEv13.x, KMB) via "User-Agent-Sniffin'", simply because they report a Chrome/86[/87] slice inside their default UA string... So far, they're not many , but this is expected to change in the future ... The most recent case I encountered is the one of "sciencedirect.com", after a Google Search result had pointed me to: https://www.sciencedirect.com/topics/computer-science/protected-storage I was "greeted" by: I'd have expected a "science-related" site to have implemented truly scientific means (i.e. feature-detection) to check whether "my" browser is able to display it properly, but, hey, even "scientists" must have "sold their souls" to Google and company (a figure of speech, surely, but ...) ... At this point in time, I've opted for a SSUAO rather than a "global" one via the " --user-agent" cmdline flag ; several extensions offer this functionality, I've chosen Custom UserAgent String ; you need the older v0.2.1, the last on MV2 : At last, I was then able to be "scientifically" informed using 360EEv13 ...
  14. ... Other people on XP SP3 have experienced that error, too : https://github.com/win32ss/supermium/issues/318 InitializeProcThreadAttributeList requires Vista SP2 as "minimum supported client" ...
  15. ... For those not closely following the development in GitHub , Supermium v122 has been publicly released: https://github.com/win32ss/supermium/releases/tag/v122 https://github.com/win32ss/supermium/discussions/316 The new installer (both 32 & 64-bit) promises WinXP compatibility; the portable distributions appear to be, again, behind a paywall: https://www.patreon.com/posts/supermium-122-99791603 https://www.patreon.com/win32/shop/supermium-plus-package-march-2024-30-day-138343
×
×
  • Create New...