Jump to content

VistaLover

Member
 View Profile  See their activity

  • Posts

    2,252

  • Joined

  • Last visited

  • Days Won

    93

  • Donations

    0.00 USD 

  • Country

    Greece

 Content Type 

Everything posted by VistaLover

  1. VistaLover
    ... Apologies for the tardiness in responding to this... Indeed, reverting: - Bug 1191042 - Use CreateOffscreen for WebGL instead of CreateHeadless. - r=jrmuizel (f98fd02e59) in your "palemoon27" tree: https://github.com/roytam1/palemoon27/commit/1a712471fb1ffc702fabc8ee3dcaf5e17783a9b3 fixes ALL the issues I had with NM27 builds after package "palemoon-27.10.0.win32-git-20220723-b6b16147cc-xpmod.7z" . Below is latest NM27 release: WebGL Renderer is, again, being enabled by default, "about:support" loads as expected (without crashing the whole browser) even when the "about:config" pref "webgl.force-enabled" is toggled to "true" ... Many thanks!
  2. VistaLover
    Many thanks for your presence here and your moderate/kind language . To the best of my knowledge, this was not a request for you inside these forums ; "official" (as in by MCP) Bk never came with support for XP/Vista (while that was true for its initial fork point, Mozilla Firefox 52.6.0); what was probably meant is that you do not declare full-blown war against the Serpent 52.9.0 fork by Roytam1... While the main dev, myself and several other "advanced users" of St52 ALWAYS make it clear that St52 != Bk, some of the (newer) St52 users on XP occasionally turn to the official PM forums for St52 support; this is wrong on them, albeit a small "nuisance" for you that you "should be prepared" to live with for as long as these users can't tell apples from oranges ; kindly redirect them here until, as you said, you remove the "Serpent" unofficial branding from Basilisk (which, hopefully, reduces the number of these "occasions") ... What is really hoped for "here" is that you "accept/acknowledge" the existence of the "fork" and that both user groups (Bk+St52) mutually benefit between them... I am much grateful for that ; a second laptop in my household still runs Win7 SP1 x64 on 2010 era H/W, with only 4GB of RAM; 32-bit Bk runs better there, without depriving the OS from needed resources to concurrently run other applications... Perhaps you could also accept Basilisk-specific verified bugs in another section of the MSFN forums, possibly in https://msfn.org/board/forum/200-web-browsers ? Yes, this is crystal clear and shouldn't be expected of you ... Since I spoke of Basilisk-specific verified bugs, kindly revisit below report: https://forum.palemoon.org/viewtopic.php?p=231584#p231584 I verified it in my own Bk-52.9.2022.08.06 x86 installation; the default setting for PDF files in Basilisk is to "Preview in Basilisk"; with that setting enforced, the embedded PDF.js viewer should be triggered to open (on-line/local) PDF files inside a browser tab[/window]; but in your latest Bk Windows build, the resultant tab[/window] is blank ... OTOH, Serpent 52.9.0 (x86) doesn't suffer from this; the OP's on-line PDF file, https://www.ipcc.ch/site/assets/uploads/2018/02/WG1AR5_Chapter12_FINAL.pdf opens, as expected, in the native PDF viewer, inside a browser tab (the file itself is ca. 35.5MiB in size, so the speed at which it fully renders depends on your connection...). Welcome to MSFN, my kindest regards !
  3. VistaLover
    What made you think that latest NM28 would behave differently in rendering web content between (first) Win7 and (then) WinXP? If the site in question renders broken in Win7, there's almost certainty it will do so under XP... The opposite is not always true, when the site's server performs UA-sniffing and blocks loading/rendering simply based on the OS (XP) reported in the UA... Already reported upstream: https://forum.palemoon.org/viewtopic.php?f=70&t=28747 Sadly, it's not; as your posted Error Console Log says, this is due to missing Regex Unicode Property Escapes support in UXP ; upstream have open issues for it at: https://repo.palemoon.org/MoonchildProductions/UXP/issues/1282 (=> https://repo.palemoon.org/MoonchildProductions/UXP/issues/1286 [closed, unresolved] =>) https://repo.palemoon.org/MoonchildProductions/UXP/issues/1675 but they have seen little action as of late... TL;DR: Switch to a Chromium-based browser for Google's proprietary services... (... perhaps the palefill extension can be enhanced to add such missing support into UXP-based browsers, but it's not ready yet... )
  4. VistaLover
    Someone else already posted about this on Aug 7th: https://msfn.org/board/topic/182647-my-browser-builds-part-3/?do=findComment&comment=1223526
  5. VistaLover
    All Basilisk-related infrastructure was transferred to the new owner/maintainer of the Basilisk/UXP application: https://forum.palemoon.org/viewtopic.php?f=61&t=28657 The ABBO "service" was configured to accommodate the app's new owner: https://forum.palemoon.org/viewtopic.php?f=61&t=28657#p230858 The most-up-to-date Bk release is v52.9.2022.08.06, available also as a 32-bit compile! ... Well, actually no ; the "EoS" Basilisk version released by MCP was (as a 64-bit compile, only) v52.9.2022.01.27, so just over 7 months ago... That version was built on the ill-fated GRE platform and had no internal updater - that is, you have to fetch and run the standalone setup for 52.9.2022.08.06 in order to update it...
  6. VistaLover
    In my Serpent 52 copy, I have: (for APMO) general.useragent.override.addons.palemoon.org;Mozilla/5.0 (Windows NT 6.3; rv:68.0) Gecko/20100101 Goanna/5.2 Firefox/68.0 PaleMoon/31.2.0.1 (for ABBO) general.useragent.override.addons.basilisk-browser.org;Mozilla/5.0 (Windows NT 6.3; rv:68.0) Gecko/20100101 Goanna/5.2 Firefox/68.0 Basilisk/52.9.2022.08.06 I'm on a 32-bit OS myself, so I spoofed Win8.1 x86 as the OS - you can modify this to suit your personal case/taste... Too old a spoofed browser version will get you the "Update Pale Moon (Basilisk)" warning in the add-on(s) page(s)...
  7. VistaLover
    Yes, PM-28.10 LPs aren't fully compatible with NM28.10.6a1; but most areas of the GUI a "general" NM28 user would frequently access function adequately... Web Developer Tools and some other "advanced" GUI areas might have "glitches" (or don't even open at all...). FTR, New Moon (both v27 and v28) was NEVER meant (by roytam1) to be localised; the fact that "upstream" PM language packs once used to work fully with past versions of NM28 was, of course, a welcome one by NM users, but also one more point of contention by upstream, who licence the PM LPs to be used exclusively on their own "official" application; if left unmodified, PM LPs, when installed in NM28, will turn the "unofficial" NM branding to "official", copyrighted, PM one...
  8. VistaLover
    i.e. "general.useragent.locale" from "en-US" to whatever the installed LP is (I suspect "ru" for OP...); NB: A browser restart is required for the change to take full effect!
  9. VistaLover
    @Anbima As NotHereToPlayGames told you, the site referenced fails to function properly in 360EEv11 because it requires the JS feature called "the Object.fromEntries() method", which was first implemented in Chromium 73 (while 360EEv11 is Ch69-based): ... hence the link to your previous post of Aug 18th (but you've also asked this on Aug 4th and Aug 6th and Aug 17th ) ... Missing "methods" can be polyfilled (please search what a "polyfill" is) and polyfills (in essence, pure JS code written in a syntax compatible with previous standards that the deprecated browser supports) can be inserted in pages via UserScripts; you need to install first a userscript manager, like Tampermonkey (closed-source) or Violentmonkey (open-source, it's the one I use, but v2.13.0 will be the last properly supporting 360EEv11) and write a simple userscript containing the polyfill code... If you're not bothered to even learn how to compose a VERY SIMPLE userscript (that works selectively on shop.brink.eu or, even, globally in the browser), this tells us that you probably like to be "spoon-fed", which won't make you appear very "attractive" in these places... Another way to inject code (a polyfill in this case) is via an extension, but I suspect you writing one from scratch just for that would be "totally out of reach" for you... An obvious solution to your problem(s) - without needing you to learn "very complicated" things - would be updating to a later version of 360EE, v12 (Ch78-based) or v13/13.5 (Ch86-based); on the plus side, many more "recent" sites will be better supported; on the minus side, your (probably old) H/W might not bode well with them... A sort of "spoon-feeding" solution would be to install below extension: https://github.com/InterLinked1/chromefill It isn't available as a .CRX file, but you need to install from zip while being in (extension) Developer Mode (or you can convert the zipped source into a CRX via the browser itself and then install that CRX); the extension provides polyfills for Object.fromEntries and several other methods missing in Chromium 70... Most of the rest of your eventual questions can find answers if you type them in your browser's Search Bar...
  10. VistaLover
    @roytam1 : Upstream UXP issue #1977: https://repo.palemoon.org/MoonchildProductions/UXP/issues/1977 Upstream implementation: https://repo.palemoon.org/MoonchildProductions/UXP/commit/28e73defa3021293bfd220bbceed04d04fd169e7 https://repo.palemoon.org/MoonchildProductions/UXP/commit/8a10b7bf8b45952f862f07842d0efb12c4feff04 "Your" implementation, custom branch of your UXP fork tree: https://github.com/roytam1/UXP/commit/707d74421937e75e0c0581d6ac9facbd83dd20ea https://github.com/roytam1/UXP/commit/0c5c349ca688b879c587a7509eea88de46fcc1d1 In file "modules/libpref/init/all.js", upstream have: +// Whether we should play wave files opened in a "media document", i.e. wave +// audio opened as top-level documents, as opposed to inside a media element. +pref("media.wave.play-stand-alone", true); + while you have: +// Whether we should play wave files opened in a "media document", i.e. wave +// audio opened as top-level documents, as opposed to inside a media element. +pref("media.wave.play-stand-alone", false); + i.e. "they" default to "true", while you default to "false"; why?
  11. VistaLover
    ... Just a small "tidbit", if you will... While FxESR 52.9.x doesn't support the final Draft 28 (later known as RFC 8446) of TLS v1.3, it has support for a previous draft (26?), that can be enabled via setting: security.tls.version.max;4 While the majority of TLSv1.3-enabled sites won't accept that "non-final" draft, a few will; case in point being: https://clienttest.ssllabs.com:8443/ssltest/viewMyClient.html which will report for FxESR 52.9.1 that:
  12. VistaLover
    ... Spoken like a true mathematician!
  13. VistaLover
    ... This has come up before in these forums, but @mina7601 is definitely a "he"... Depends on how old.... If you're referring to Chrome 49, EoS version for XP SP3 (SSE2), no, it can't cope adequately with the web of 2022 ... Should use the 360EE forks, based on later Chromium versions (69/78/86) ...
  14. VistaLover
    OT : This must have set you back a small fortune, hasn't it? High-End H/W is constantly on the rise here price-wise, due to 1. shortage of rare-earth metals (and other semiconductors) used inside electronics chips 2. exorbitant rises in energy costs (natural gas, electricity, petrol, etc.) - in part due to the Russia-Ukraine conflict - which is reflected in elevated production/transportation costs ... A laptop of those specs can easily cost something near (or above) the neighbourhood of 1,000 Euros here, when the average (monthly) salary is considerably below that ... Take good care of your high-performance laptop, then...
  15. VistaLover
    This is indeed correct - most UXP-based browsers are now natively supported in palefill's install.rdf file; it's only Serpent 55 that isn't: https://github.com/martok/palefill/issues/25#issuecomment-1157015223 @Mathwiz is mainly using St55, so perhaps got confused and assumed this is still the case for UXP-based browsers ...
  16. VistaLover
    This isn't true ; with the last (semi-)official release (v.1.2.19) of github-wc-polyfill prepared by SeaHOH, the GitLab link posted has no problem fully loading in my latest Serpent 52 copy (manual modification of 1.2.19's install.rdf is required to allow installation in St52): NB that SeaHOH has abandoned further development of github-wc-polyfill, but our own @roytam1 has provided (at least two) updated XPIs for it in below "upstream" issue #68 thread: https://github.com/JustOff/github-wc-polyfill/issues/68#issuecomment-1218104421 So one should install v1.2.19.2 now to keep up with GH's shenanigans ... OT: MSFN's post/comment editor is overly problematic today, I find ...
  17. VistaLover
    ... Well. most application authors currently behave like sheep , blindly (no offence meant, BTW ) following ONLY what Microsoft supports at the time they release an update for their app... My gut feeling is they didn't go for DirectX 11.2 specifically, rather they dropped support for previous DirectX versions, as these are to be found in OSes MS no longer supports (free of charge, as in not ESU ) ...
  18. VistaLover
    ... Why would you be off-topic if your query pertains to Serpent 52.9.0 ? Well, here's the long story of it: My complete theme is called Photonic and it was created by Lootyhoof, a member of the upstream MCP dev team, who specialises in Complete Themes for the Pale Moon browser! Photonic had originally support for both Pale Moon (which has a pre-Australis default theme) as well as support for (official) Basilisk (which has the Australis GUI). As such, it was hosted in both https://addons.palemoon.org/themes/ (where it still is) and https://addons.basilisk-browser.org/themes/ In late January, Moonchild halted further development of Basilisk; in May, Photonic was removed from: https://addons.basilisk-browser.org/addon/photonic/ (archived snapshot: https://web.archive.org/web/20220511055801/https://addons.basilisk-browser.org/addon/photonic/ ) Lootyhoof continued the theme's development, but he removed Basilisk support in versions > 4.0.0... The source code repo for Photonic is: https://github.com/Lootyhoof/photonic A no-longer-maintained mirror is: https://repo.palemoon.org/Lootyhoof/photonic The easiest way to get the last Basilisk-compatible version of Photonic is via GitHub: https://github.com/Lootyhoof/photonic/releases/tag/v4.0.0 But (there's always a "but" for us on "unsupported" OSes+forks), getting that XPI is NOT enough, sadly... As you might know already, (official) Basilisk is meant to run on Win7+, so Photonic's author made sure to use Win7+ specific CSS code during its development ; many of its internal CSS scripts have the below code: @media (-moz-os-version: windows-win7) { which makes sure the theme (is designed for and) properly runs at minimum on Windows 7, only! Additional specific code @media (-moz-os-version: windows-win8) { and @media (-moz-os-version: windows-win10) { configures the theme on Win8/8.1 and Win10 - there's absolutely no provision for the theme running under XP and/or Vista, which are the target (i.e. most frequently used) OSes for Serpent 52.9.0 users... Fortunately, its install.rdf file is compatible with St52, so it doesn't require any modification to install the theme there... But: I don't have XP here to check, so I have no clue how the theme behaves (if and at what degree it works) under an XP installation of Serpent 52.9.0... All I can tell you is that when I first installed it in my Vista SP2 installation of St52, the tab bar was BROKEN/mostly unusable; I had to unpack the theme and apply trial-and-error many times, adding several additional "(-moz-os-version: windows-vista)" conditionals to select script places, to get a properly working tab bar on Vista, keeping full Aero support, too... Along with the theme itself, I'm also using the "Classic Theme Restorer v1.7.8.2019.10.27" extension (by Aris), to further modify it to my liking... A glimpse of what it looks like as I type this is: I understand Photonic (being an abandonware for Basilisk, at least for now) is susceptible to future partial/complete breakage, as Serpent 52 is being further developed - though, TBH, I don't expect "deal-breakers", as "upstream" very infrequently touch the GUI code; some minor bugs did fall under my radar, but I'm willing to live with them for the time being... So, now you know!
  19. VistaLover
    With respect, the way I understood his query was that he wasn't disputing whether package files whitelisted by ALL VT engines exist, but how many of them in total... It would appear the two of us interpreted somewhat differently @Dave-H's query, but only he can clarify that further ; all's well, BTW . It's the same web extension (but in .CRX format) I had advised installing in all three 360EE variants, which lack a native spell-checking feature . Thanks for your kind words you two , but I'm not worthy of more praise than any of the rest of the MSFN members/volunteers, who offer help to others out of their spare time (I'm actually typing this being on vacation) and without charging a (euro)cent for it! I find I can't be omnipresent in all the various places of MSFN, so, Mozilla-based browsers being a field of expertise, I tend to offer help there (and now I should probably stop derailing this thread any further ... ) ! tschüß
  20. VistaLover
    ... Right ! Like you, I need to put my (presbyopia) glasses on... I now see (glasses on) that the VT test refers to "ProxyPopMenu.bat" file... He in fact wrote: Which browser is used to post these? Installing an en-US/en-GB dictionary in the browser and enabling spell-checking will flag misspelled English words as you type them, before you make the post public (i.e. submit it); that way, you can still improve your English along the way, but keep your posts (mostly) error-free ! E.g. in St52, if I misspell its past tense, "misspelled", it would appear as below: That way, I'm alerted I typed something wrong and then try to correct it!
  21. VistaLover
    Hmmm... The picture only shows that all which AV engines whitelisted the complete package file "ProxyPopMenu.bat", NOT which files inside the complete package were found to be benign, which, I believe, was what was actually queried by @Dave-H ... ... English lesson of the day! Should've been: "Batch files themselves" (if you were going to use the plural number ) ... Thanks for your efforts, BTW!
  22. VistaLover
    This behaviour is controlled by a Google SSUAO; latest Serpent 52.9.0 has it as: general.useragent.override.google.com;Mozilla/5.0 (%OS_SLICE% rv:71.0) Gecko/20100101 Firefox/71.0 Basilisk/52.9.0 i.e. it spoofs itself as Fx 71.0; result: (that one above is with its dark theme enabled - selection is stored inside a cookie ) If you're in the habit of using localised Google TLDs (e.g. google.co.uk) other than ".com", you need create additional SSUAOs for these...
  23. VistaLover
    Most unfortunately, @martok isn't willing to "fix" Bank sites in UXP-based browsers through his extension : https://github.com/martok/palefill/issues/38#issuecomment-1192738141 The reasons he cites are security-related ...
  24. VistaLover
    Welcome to the MSFN forums! As a general rule, consulting your browser's Web Console/Browser Console/Error Console will provide useful hints/clues as to the "why" : ... and even if that's "Greek" to you, it'll give prospective helpers a general idea... The ING Bank site relies heavily on customElements, a web spec (part of the Web Components JS+CSS framework) discussed, by pure coincidence , in posts of this thread's previous page... CE/WC is a technology originally created by Google (they currently are the only ones who dictate how the web should evolve ), the upstream developers of UXP/Pale Moon, due in part to their aversion of anything Google, put WC support inside UXP in the "back-burner", so to speak; truth be told, there still exist major technical issues to backport/glue-in all of WC to the platform, which, as you might already know, evolved from a now quite "old" Mozilla Firefox forkpoint... CE/WC are currently behind a disabled pref, in an incomplete/immature developmental state... Third party extension authors try. with various success and targeting selected URLs only, to mitigate lack of CE/WC support in UXP-based browsers ; at this point in time, the extension which holds the best promise for UXP users is one maintained by your compatriot Sebastian Hütter, aka martok, which is called palefill: https://github.com/martok/palefill/releases Install the XPI file linked in that page and then kindly ask him to include support for ING Bank, by filing an issue (GitHub account required): https://github.com/martok/palefill/issues From my initial testing, implementing support would be as easy as adding in file "./lib/builtin-rules.js" below code: exports = String.raw` +www.ing.de + std-customElements +! -- developer.apple.com std-customElements For your convenience, I have prepared myself a patched XPI file of palefill, (.XPI file attachment removed on 202208160022Z) that you are free to test; works as intended here (under latest St52): Later addition: Bank sites are a major pain in the posterior for "legacy"/non-mainstream web engines, because Bank IT staff insist on using the very latest Web Specs in them (even ones that haven't yet made it to final state, though this is not the case for CE/WC), as they think it gives the higher members of the Bank's hierarchy (who probably know little about web development), as well as most of the Bank's clientele, a false sense of "on-line security" ... I'm not saying Bank sites should stick to TLS 1.0/1.1 to merely satisfy old browsers, but not always using the latest Google-derived "shinies" won't make their sites (and their customers' interactions) less secure, would it?
  25. VistaLover
    This is a known and long-standing issue for both UXP-based browsers (such as Serpent 52.9.0), as well as the test Serpent 55.0.0/moebius builds... https://repo.palemoon.org/MoonchildProductions/UXP/issues/1344 (Part of https://repo.palemoon.org/MoonchildProductions/UXP/issues/1361 ) ... Turns out I had already toggled "dom.enable_performance_observer" in Serpent 52.9.0, too, without even realising ; so it appears that the default setting in UXP-based browsers as well as in St55 is to have "PerformanceObserver()" disabled, for whatever reason...
×
×
  • Create New...