Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 04/20/2023 in all areas

  1. I've got similar score as @Anbima in Speedometer 2.0 on XP in 360Chrome 13.5, using AMD Phenom II X4 920 (over)clocked at 3 GHz. Don't recall the exact number, should be somewhere between 36 and 39. Seems simply CPU bound test.
    2 points
  2. I still say you need a better test site. DcB and Mini don't even render the same page for me. One centers the Home menu at the bottom of the page, one has "star" numbers, the other does not, so one browser clearly had to do something different to get that "star" number. I get several png's that don't even load due to err_cert_invalid, so of course that is going to effect page load time. Page loads in under a second, but the browser's own Dev Tools Network tab reports "Finish" at closer to SIX SECONDS - the load time is being "tricked" to report LOW.
    2 points
  3. Does the one hosted on AMO not work for you? https://addons.mozilla.org/en-US/firefox/addon/saveasebook/versions/ It does install in latest St52, but haven't tested its proper function there ... ... Which files? From a quick look, one should only pack to ZIP(=>.xpi) the contents of: https://github.com/alexadam/save-as-ebook/tree/master/web-extension
    2 points
  4. Fixed. For how long is another question. palefill-1.26.3.xpi
    2 points
  5. Perhaps one could define static methods (functions?) back then, but not properties. This works in UXP: class TestClass { static shoutHello(num) { alert(`Hello! You've passed the number ${num}.`); } } TestClass.shoutHello(123); This doesn't: class TestClass { static num = 123; static shoutHello() { alert(`Hello! The number in here is ${this.num}.`); } } TestClass.shoutHello(); And this does: class TestClass { static shoutHello() { alert(`Hello! The number in here is ${this.num}.`); } } Object.defineProperty(TestClass, "num", {value: 123}); TestClass.shoutHello(); But gets messy.
    2 points
  6. I'm pretty certain this "term" has been mentioned and explained numerous times over the course of time in "these" threads... When upstream (MCP) had to finally move away from the Tycho application platform (fork of Mozilla 38esr) Pale Moon 27 was built on, "they" first opted to rebase their platform on a Mozilla 53.0a1 (Nightly) code snapshot, with few bits here and there from 54.0 & 55.0; that "experimental" platform was given the codename "moebius" (aka UXP Take 1); the test browser application "they" built on top of it was baptised Basilisk; the original Basilisk was given an appVersion of 55.0.0 for purely "sensationalistic" reasons, as it had very little to do with Fx55, codewise... Roy's fork of that one was, of course, Serpent 55.0.0 ... After a while, "upstream" discovered (the hard way) that this experimental platform they called moebius was not good for their intent and purposes (i.e. build Pale Moon 28 on top of it), so they ditched it altogether and started from scratch on developing a second platform candidate, that one forked from Mozilla 52.6.0esr; the result of those efforts is UXP (Take 2), the test browser application built on top of it was, again, Basilisk (but this time its version had the "52.9.year.month.day" format) - Pale Moon (in its v28) was successfully migrated from Tycho to UXP, where it continues to build on now; MCP had said back then that it's impossible for them to rebase PM's platform to a Mozilla platform > 52.x.x, but who knows what the future will "dictate" ... When MCP moved away from MS's GitHub (because it stopped being compatible with the browser they were developing - and MS had no intention of keeping backwards compatibility with "legacy" browser engines ), MCP removed completely the moebius source code from there; but Roy had kept a fork of it, which he continued to sporadically maintain, with code fetched from other "upstream"; he would then post monthly builds of Serpent55/moebius... In more recent times (thanks to additional spare time due to pandemic lock-downs ), an effort was undertaken to bring the "old" moebius platform "closer" to the UXP platform currently developed by MCP and the release cycle has become weekly... I occasionally test St55, but I am a St52 "person" myself... St55 has slightly better Web Extension support (inherited from Fx53.0a1), slightly better Tab Containers support, probably (slightly) better e10s support and a better GUI for its standalone media player; all of these "features" are there on a "use-at-your-own-risk" state, because no-one maintains those aspects of St55 code... And its JS engine isn't 100% on par with UXP's, still... But whatever anyone prefers ...
    1 point
  7. Quoting myself, thats also why Unifi has gotten fairly popular- they provide in my opinion one of the best services for networking. For businesses, the importance of a simple network that is powerful, and easy to use, is the reason Cisco networking has been dying off in the business world, and only still remains in data-centers. However eventually that will change. My home network runs on a Unifi AP from 2019 and it has performed exactly the same since we have gotten it, and has been the most reliable WiFi AP we have ever owned.
    1 point
  8. Thank you, I now feel even more interested in using this tool after reading this part.
    1 point
  9. ... The last version of which is v1.70, from 2020... The app is tailored to work best with official Mozilla Firefox, properly installed in the system... For XP x86, you obviously need to DL the 32-bit flavour - localization file needs to be separately downloaded/extracted and placed alongside the main executable... Once launched, don't fear if the window ends up being empty : Top Menu => File => Select Folders => Profile Folder Path: ... and paste there the full (absolute) path to the browser profile directory holding the account credentials you wish to extract/back-up; as you might have figured out already, the app also works for "portable" browser installations! FTR, just used it on latest St52 (32-bit), so it definitely works on UXP-based browsers ...
    1 point
  10. I'm getting high / highest CPU utilization in both Spt.52 and NM28.10 (latest versions of 04/07 and 04/15) on various sites when JS is activated, eg. https://www.ebay.de or https://www.commerzbank.de/ Didn't observe that behavior with the late-march versions (and Palefill 1.26). Edit: Sorry, wrong observation: the same heavy CPU utilization now persists when reverting to older Spt./NM versions. There must have taken place some JS modification the last days coincidently on several sites, www.commerzbank.de/ is one of them.
    1 point
  11. Even better when 30 of us aren't on an MS Teams meeting with two other continents and that's just our department.
    1 point
  12. He is referring to St55, it is not in the version info but every time roy posts a new St55 release he states: > New build of post-deprecated Serpent/moebius for XP!
    1 point
  13. The "latest" St52 and St55 are not being sent the same HTML as being sent to other browswers (including older St52 and St55). The "latest" St52 and St55 are not being sent the visibility: hidden for the <body> tag. No clue "why", changing user agent did not get the "latest" St (forgot if I tested in 52 or 55) to be sent the visibility: hidden. Limited investigation, could not isolate "why", but this will give you a headstart into something to look for - why is that visibility: hidden being sent to older browser's <body> tags but not to "latest" St's ???
    1 point
  14. Oh! That explains a lot...it is good to finally have Web Components support. I did learn recently about UXP gaining support for this, but didn't realize it directly affects the ability to use GitHub without Palefill. Thank you for the explanation! (And thanks for not making me feel like an id*** about it...) I would like and do want to learn more about JavaScript, operators, etc. Though I fall into the category of your typical user (as opposed to a programmer/contributor), I don't want to be totally ignorant of how everything works...honestly, it's just amazing to go back to NM28 and see all the changes that have been made as of late. I'm finding NM28 is still very good and reliable as a 'base' browser...and for the sites that have issues in it, I'm glad there are other alternative browsers, like 360 and Mypal68, to use as well. Roy has definitely made a tremendous effort over the years with his browser forks. I am always excited to try a new release, even if there's the occasional bug...the fact that there are still browsers being maintained and updated for XP users is amazing, doubly so that it's on such a frequent basis. I feel like the XP to 7 to 10 transition, over time, can be accomplished and I feel very comfortable about it now. For now, I'm happy that I'm still able to use this legendary, venerable OS as my 'daily driver'. MS's finest hour for sure!
    1 point
  15. English is fine for testing, but not everyone is english :/ Let's find updates in more languages.
    1 point
  16. Another option is PasswordFox from Nirsoft. I have never tried it, but it is supposed to work with all Firefox profiles (and hopefully with all Pale Moon/New Moon profiles, too). Here is a link: https://www.nirsoft.net/utils/passwordfox.html
    1 point
  17. Dave-H is always fair, one of the many positive qualities I like and respect in Dave's character !
    1 point
×
×
  • Create New...