Jump to content

VistaLover

Member
  • Posts

    2,105
  • Joined

  • Last visited

  • Days Won

    93
  • Donations

    0.00 USD 
  • Country

    Greece

Everything posted by VistaLover

  1. x86: https://www.google.com/dl/release2/chrome/adjs6spifue5dxngiogotsz633pq_109.0.5414.149/109.0.5414.149_chrome_installer.exe x64: https://www.google.com/dl/release2/chrome/oeecyq7z2j4yyfoa4cev5c4o7e_109.0.5414.149/109.0.5414.149_chrome_installer.exe Source: reddit ...
  2. While your technical analysis is correct , what "I" think was meant by Milkinis was: Website authors of this era target/expect their sites to be opened by a browser based on a "recent" (or even the latest) version of the Chromium engine (I'll throw recent/latest Firefox into this mix), which is "multiprocesses-capable" and has multiprocess turned ON by default; it's even more "effective" in Chromium, as there's a separate process for each tab (by default) ... Website authors of this era are also "lazy" and would not design a page from scratch, instead they use pre-made templates and frameworks/webpacks, that also target a "recent" (or even the latest) version of the Chromium engine ; website authors of "today" don't particularly care about backwards-compatibility with older browser engines, especially since, some years ago, Internet Explorer 11 was thrown out of the picture (in favour of yet another Chrome clone , [Chr]Edge); and I'm sure we'll both agree that Pale Moon and the rest of the UXP-based browsers (even more "marginal" than PM itself) are well outside their "radars" ... In the comfort/knowledge a recent Chromium engine (especially on recent H/W) will be able to handle whatever one throws at it (and, even more importantly, will not alert the user if it struggles to render said webpage), these website authors will throw in "metric tons" of Javascript/CSS code, still and moving graphics galore, etc., bloating it considerably, succumbing to the recent web-design "trends" that are "supposed" to attract more viewers/"clickers" ... Invariably, these "over-bloated" websites are expected to lag considerably on the likes of Pale Moon and its "cousins", due to them being designed as single-process and having inherited several unresolved bugs (which have been discussed on and off in the relevant threads) from their initial fork-point of Mozilla ESR 52.6, that Mozilla left to bit-rot, as "they" had moved on to a different engine with Quantum onwards... In closing, I think this was the gist of: Regards ...
  3. ... FWIW, that "Original download link" now produces a "Server not found" error ...
  4. ... Indeed , but your (GitHub/MSFN) username (roytam1) isn't explicitly mentioned there, just a link (8a0897d23f) to your GitHub repo and code .,,
  5. Serpent 52 is a browser application built on (a fork of) the UXP platform, the same platform the official Pale Moon browser (by Moonchild Productions) is built on; more technically, Serpent 52 is a fork of the official Basilisk browser application, but these two forks have somewhat diverged from each other over time... While UXP was forked from Mozilla 52.6esr initially (and that was years ago), UXP-based browsers have been equipped with a plethora of recent web API technologies and the XP-compatible forks (New Moon 28/Serpent 52/a few other) have empowered "legacy" OS (XP/Vista) users to surf a very large chunk of the 2023 WWW ... Be that as it may, no UXP-based browser will be a perfect match, webcompatibility-wise, for recent versions of Google Chrome and Mozilla Firefox, especially on the many, JS-infested , "popular" sites of this era... The XP-compatible UXP-forks are being maintained by roytam1, more info can be found in the respective thread(s) ...
  6. ... and: ... Today was less hot here , thus I had a second chance to research this more diligently ... According to MDN: https://developer.mozilla.org/en-US/docs/Web/CSS/:where#browser_compatibility the ":where()" pseudo-selector was first implemented in Mozilla Firefox 78 and Chrome 88; but, as most of us know, Kafan MiniBrowser was based on Chromium 87 ; some investigation revealed that my own copy of it is able to display properly the MediaMarkt laptop/notebook entries because, in tweaking my MiniBrowser copy, I had enabled below flag: chrome://flags/#enable-experimental-web-platform-features Turns out that flag activates (among other things) CSS features that have been officially introduced in Chromium 88+; indeed, with that flag disabled (the default setting): but with it enabled (i.e. how I have it myself): Sorry for any eventual misunderstanding ...
  7. FWIW : It's quite possible something inside Dixel's browser profile isn't "liked" by imgur servers; but if he's fine with it, so am I ... Sorry again for the misunderstanding, have a good night all of you ...
  8. ... Right; so it's something along the lines of: Apologies for misinterpreting your post, but, in my defense, it was "just an image" post; the imgur links continue to display properly for me here, thus my IP has not abused their servers ; if you're impatient, you could restart your modem/router to get a new IP address from your ISP (if possible), or use some other means to evade imgur's block (assuming it's IP-based); also, several privacy-enhancing extensions/settings are known to not go down well with third party services like image-hosters ... I always upload to imgur as an unregistered/anonymous user, I have no account with them; if a "view limit" is being imposed, then it's solely on their side ...
  9. @Dixel : I can't seem to understand the gist of your latest post ; my post you seem to have referenced has 3 "linked" images (hosted on imgur) that display properly here in both Serpent 52 and 360EEv13; these image attachments won't become "dead" unless imgur go out of business... https://i.imgur.com/qNoCUd1.png https://i.imgur.com/S02zeSn.png https://i.imgur.com/pyWLAMH.png If you're somehow blocking imgur or it's simply a regional CDN issue for you, obviously I have zero control over it... If you simply wanted to comment on NHTPG's practice of: who's been using the native (but size-limited for "plain" users) file-attachment feature of MSFN, then you should have chosen one of his posts with deleted image attachments, e.g. that one ... In any case, I wasn't amused at all ...
  10. Is that Proxomitron "talk" ? Can you offer code to implement this for UXP in the UCyborg userscript implementation? PS: I can't catch up with both of you exchanging "instagram"-type messages while I prepare a "normal" post with images (which have to be edited and uploaded to a third party service) attached ...
  11. ... Please read my previous post here and try the same "laptop" entries in: https://www.mediamarkt.de/de/category/notebooks-362.html I've tried myself ca. an hour ago and the same issue (image overlap on text) manifests itself in the Ch86-based forks : ; additionally, if you had paid closer attention to the screengrab UCyborg posted here, you'd have spotted the still missing images of the notebooks themselves: Since those laptop entries display OK in [Chr]Edge 94, the CSS/JS feature "mediamarkt.de" rely on was implemented between Chromium 87-94 ... But, guess what? Kafan MiniBrowser seems to display correctly those laptop photos (I have enabled dark mode there): ... so, by pure chance, we now have an answer to your previous question in another subforum : So, it's a feature first implemented in Chromium 87 (actually, in Chromium 88; kindly read this followup ...)
  12. In case no-one here noticed it already , "our" roytam1 is now formally mentioned inside the "official" UXP repo: https://repo.palemoon.org/MoonchildProductions/UXP/commit/7f8ea9ae2f92b71eefcd1dc286baaf529cc5686a Thanks to Brian Smith (aka dbsoft), the MacOS dev member of MCP ...
  13. You are most welcome ; of course, it was impossible for either of us to know that a post on that same subject was about to be submitted imminently by another member, while in the process of putting the "finishing touches" on an already composed post of ours ; so, actually, nothing to apologise for ... Since you are a new member here, I was uncertain of the level of your "tech know-how", so I was somewhat more verbose in my reply to you; this post of mine, while proven unnecessary towards the resolution of your predicament, might still serve other people with similar issues ... Best regards .
  14. @WSC4 : Had you posted your last post some mere minutes earlier, it would have saved me (composing and) posting mine on that same subject ; in any case, I'm glad you got things sorted out on your own ... Regards ...
  15. My screenshot was with a fresh NM28 32-bit profile (+uBO, of cource ) on Vista SP2 32-bit, userscript manager being the "legacy" Greacemonkey for Pale Moon ... Same "picture" in my "dirty" Serpent 52 profile, with the EoS Violentmonkey version (2.14.0) as my userscript manager ... I don't have access currently to a Win7 SP1 64-bit machine, to try your Mozilla Firefox version (which one, exactly?) ; that laptop is on summer vacation, along with its owner ...
  16. Hi @WSC4, welcome to the MSFN forums (the last "stronghold of XP-diehards" , as someone in another forum called it), best greetings to Oz ... In general, as posted already by another member, it's not a good idea to "try" financial services in "legacy" browser engines & OSes, because these institutions usually expect the "latest and greatest" in both departments (to generate a "sense" of security for their clients...); but we'll try to help, if we can; then, it's up to you to follow any offered workaround ... For starters, when I load the posted link in my FxESR 52 copy, I get a "warning" banner: Since you wrote already that FxESR 52 "works" for you, I'm inclined to disregard this "update" warning ; however, following the "Learn more" link it contains will land one on: https://www.westpac.com.au/personal-banking/online-banking/support-faqs/supported-browsers/ Reading that article immediately gives the impression it hasn't been updated (pun intended) for quite a while; Fx>=52 ? Chrome >=58? In the OS entries, no mention of Win8.1/10/11 (?); if it's minOS requirements, then it's obvious they don't support WinXP anymore (but you said FxESR 52 worked in your WinXP SP2 64-bit machine ) ... If we take that table "seriously", then UXP-based browsers (NM28, St52, etc.) have engines far superior to the one FxESR 52 has... Based on my small analysis above, and without having any failure details from you (Web/Browser/Error Consoles of NM28), first thing I'd suggest is a SSUAO (site-specific-user-agent-override) on NM28 targeting that bank, in the hope they're simply rejecting NM28 based on its default user-agent string (a practice known as UA-sniffing) ... If you had been lurking here "silently" for more than a year, perhaps you're already familiar with the procedure; if not, then: 1. In NM28, open a new tab and in the URLbar type about:config - press enter, and then press the "I promise to be careful! button"; you should now be inside the advanced preferences interface 2. Place your cursor inside the existing entries and right-click, invoking the context menu 3. from the CM entries, select New -> String 4. in the preference name field, enter general.useragent.override.westpac.com.au and click OK 5. in the string value field (in the second pop-up), enter Mozilla/5.0 (Windows NT 6.3; rv:52.0) Gecko/20100101 Firefox/52.0 and click OK Done! You should now have created a new entry that looks as below: Restart your NM28 browser (just for good measure ), then try your "bank" site anew; this time, the bank's software will think you're visiting with Fx52 on Win8.1 ... Tell us how it went! Cheers ...
  17. @UCyborg : With your "(mediamarkt|saturn).de" userscript applied, I get on some occasions graphics overlapping text: https://www.mediamarkt.de/de/category/notebooks-362.html Can you investigate a fix? Thanks ...
  18. ... And, believe it or not , I do agree with you on this ; one other serious irritant for me is the preposterous waste of screen vertical space due to their very "tall" address bar: Agreed, too... Grabbed just half an hour ago ; disclaimers: 1) I don't use a NHTPG/HO modded version, 2) as can be seen, I'm using the 360EEv13 dark skin...
  19. ... I don't think, personally, an apology was owed ; those who follow closely this thread should have already been aware of the original post mentioning Kafan (albeit in a 360EE topic): FWIW, I, too, dislike this "behaviour" and, to this day, have not found a way to override it ...
  20. Correction : Mozilla, aping Google to the letter, but with a delay of a few years, put Vista SP2 on the same boat as XP SP3; FxESR 52.9.x was/is the last version of Firefox to run on (plain) Vista SP2; release channel v53.0.x. could be "hacked" to launch there, too, but with serious shortcomings in the media playback department... TL:DR: Fx 53.0+ requires Win7 SP1 and higher (obviously, I'm not talking here about Vista's 64-bit Extended Kernel implementations ) ...
  21. https://newsweb.oslobors.no/message/407334 https://en.wikipedia.org/wiki/Opera_(company)
  22. Well, who would have thought? German sites/services not loading properly in "our" legacy browsers? "Dirty" workaround in Serpent 52: Pick only one (doesn't matter which) on the list of below four "about:config" prefs: layout.css.all-shorthand.enabled;true layout.css.is-where-pseudo.enabled;true layout.css.legacy-negation-pseudo.enabled;false layout.css.unset-value.enabled;true ... and toggle its value; then the sites will render OK: As I am unsure of the eventual effect on other sites, once you're finished with MM/Saturn, reset the pref you initially selected ... Regards
  23. ... Can you also test whether "github.dev" now loads successfully in UXP? Below screengrab is with latest NM28: Although, besides the BigInt one, there's another alarming TypeError: Thank you so much ...
  24. Thanks ; however, UAC was turned off from the very start this Toshiba laptop, with Vista OEM 32-bit, came into my possession ...
×
×
  • Create New...