Leaderboard

No. The problem lies in the fact that noone has a clear idea of what testing or validation is, and programs are written, more often than not by lazy/sloppy programmers, but also by good, attentive and knowledgeable ones, that do not know anything about the actual processes involved (because there are always one or more middlemen involved, so that the actual final customer, the guy/gal that actually has to use the program or maintain/service the machine never communicates directly with them and viceversa). The program is anyway always late and what is released is invariably - in the best cases - an early beta, and all the bug finding and reporting is demandated to the client, that normally has no idea on how this is done (remember, the client is the one that pays the money to buy something that he has not the capabilities to develop in-house). It is peculiar (and I believe rather unique to the (largely bad) software industry to provide "solutions" that are not working (or not fully working) AND to put the blame on the clients (you know, again, the ones that actully pay for the service) OR asking them to lose hours, days, weeks into troubleshooting the crap they produced. More loosely it is called "professionalism" and most of the software industry has no idea of what it is. Imagine you go to your barber and he after taking your (good) money for a haircut gives you a pair of scissors telling you "If in the next few days you see some tuft sticking out of your head just cut it off" or - which is what the large software companies do - "You also owe me 100 bucks for a week of assistance, if you see some tuft sticking out you just drive here and I will cut it", or - alternatively - "In case you notice some hairs sticking out call me an I will be happy for a mere 200 bucks to come to your house and cut them level with the rest". Then you go to get your car from the mechanic and he tells you "Ok, I changed the tires, I am pretty sure that I did tighten the nuts properly, should you lose a wheel, don't worry, it is covered by warranty, you just bring me back the old wheel and I will fit a new tire on it for free". Then you go to a restaurant and the cook tells you "The food I prepare is fine, should you by any chance get poisoned i will reimburse you part of the bill". jaclaz

I'm on v1.16.4.14b2 since yesterday My installation was on an extremely heavy New Moon 28 profile: tens of extensions, many userstyles installed (within Stylem), many userscripts installed (within GM-for-PM), that means it's not a "snappy" profile to begin with ; so I can't make any remarks regarding uB0 related performance issues... I guess the proper thing to do is to install ONLY the beta on a fresh NM28 profile and then submit it to various benchmarking tests; but I couldn't be bothered, to be frank For more info, I'd keep an eye on https://github.com/DandelionSprout/adfilt/issues/7 https://github.com/uBlockOrigin/uAssets/pull/6808/ https://github.com/gorhill/uBlock/pull/3765

Special message from upstream: https://forum.palemoon.org/viewtopic.php?f=1&t=23605 (and https://forum.palemoon.org/viewtopic.php?p=181666#p181666 )

Not weird at all. It is one problem with using Embedded OSes, you don't know what you are missing until you run into a problem. The issue being is that most software developers (or ISVs) write their software for, and test it on, retail Windows XP. When the time come to move to an Embedded product, presuming they are not opting for an Enterprise SKU, the OS is built from the ground up. The client sends a list of requirements, and a demo installation is created and sent to the client.* The client tests their software with their hardware and makes reports back any problems. The Embedded Partner then adjusts the OS and the ISV will retest until they are satisfied. Then the unit gets approved and is put on site somewhere. The problem lies with situations where the client doesn't test for all situations that their product would be involved in, or they may not communicate a need properly. Then on the other side, the documentation of what package does what is not detailed enough when building an OS. So these things do end up happening. There are also situations where an expected OS component you would think is enabled by default ends up not. One example I can think is that even if you install the USB package for Windows 8.1 Industry Pro, USB (bi-directional) 2.0 or 3.0 doesn't actually work. One client I build this OS for got all the way past testing phase and had units on site when it was determined their machines did not have fully functional USB. The issue was discovered when they tried to do firmware updates using USB keys. There have been other situations where expected low-level functions are missing, and since they are not documented properly, can take a while to figure out. Another I recall is an OS (I forget which Embedded SKU it was) didn't support the function of RS232 (Serial Port) but did install the drivers for the device. *This example follows the ISV/Embedded Partner model and not the in-house model.

Yes, I was aware of that, but Google is greedy and their new YouTube layout works smoothly only with a Chromium based browser. Here is a rough explanation of why that is: [Click To Open Twitter] So really, using it on roytam1's browser is not a very good option regardless. Please keep in mind that I do not have experience with the newer and more resource heavy layout on older hardware as I have been using XP on a modern computer and performance has never been a problem for me, so it might not be as noticeable on older computers as it is on newer and more powerful ones. More smoothly than any other non-chromium browser with a spoofed user agent, yes. Also, neither the last official Chrome (49) that works on XP or the Advanced Chromium (54) support the new layout, even with a spoofed user agent. (The layout does not load properly and does not work, at least to my knowledge) Layout, to be more precise. Please excuse me for the confusion that I may have caused due to English not being my primary language. Right on point.

... Trouble's in the air for uB0-legacy : https://forum.palemoon.org/viewtopic.php?p=181590#p181590 ... and following posts... Betas of v1.16.4.14 : https://github.com/JustOff/misc-pm-stuff/releases/ (... but the "on-the-fly" rule conversion to the old format, supported in uB0-legacy, does result in performance degradation... )

Nope. If you were to remove the user agent override from roytam1's browsers, you would see the newer design.

Hi ~♥Aiko♥Chan♥~ In vanilla Windows 98 SMPlayer 0.6.7 me thinks was the latest that could be used, but SMPlayer's seek bar does not appear functional either, it's greyed out. SMPlayer just opens up the video in 'mplayer', where the OSD (on screen display) shows video time by toggling the letter 'o' key and the arrows allow going back/forth. That's when using it in Windows. When launched via Cygwin, the OSD does not work or i don't know how. Sorry your original post just indicated does MP4 work, no mention of the seek bar. In VLC 0.8.6d MP4 and the seek bar work, although i believe you may be right about issues with large video files. May test more thoroughly later. Sorry to sidetrack, this doesn't solve your Windows 95 issue.

The member site has a security flaw, and will not open in Firefox or IE 11. I would like to retrieve my key, but it will not open.

no, it can be anything you received from remote, for example, HTML, CSS, images, videos, audios, etc.

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rths.ml/boc-uxp/mailnews.win32-20200111-beb2221f-uxp-f64e760ab-xpmod.7z Browser-only Suite Win32 https://o.rths.ml/boc-uxp/bnavigator.win32-20200111-beb2221f-uxp-f64e760ab-xpmod.7z source patch (excluding UXP): https://o.rths.ml/boc-uxp/boc-uxp-src-xpmod-20191123.7z There are no new Official repo changes since my last build. For UXP changes please see above.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.ml/basilisk/basilisk52-g4.5.win32-git-20200111-fd382bb-uxp-f64e760ab-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.5.win64-git-20200111-fd382bb-uxp-f64e760ab-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rths.ml/basilisk/basilisk52-g4.5.win32-git-20200111-fd382bb-uxp-f64e760ab-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rths.ml/palemoon/palemoon-28.9.0a1.win32-git-20200111-b7841e5cf-uxp-f64e760ab-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.9.0a1.win64-git-20200111-b7841e5cf-uxp-f64e760ab-xpmod.7z Official UXP changes since my last build: - Issue #1338 - Part 1: Update NSPR to 4.24 (f7d301332) - Issue #1338 - Part 2: Update NSS to 3.48-RTM (f4a12fc67) - Issue #1338 - Part 3: Update NSS symbols (c097dcf7f) - Issue #1338 - Part 4: Initialize NSS with desired run-time values. (24f97a168) - Issue #1338 - Part 5: Clobber for NSS update (b1694ef0a) - Merge pull request #1341 from MoonchildProductions/nss-work (e30d68b69) - Issue #1345 - Implement non-standard legacy CSSStyleSheet rules (b4d686d62) - Merge pull request #1346 from JustOff/PR_CSSStyleSheet_legacy (c66b70c4d) - Reject sample rates that are out-of-range for libsoundtouch. (c03265177) - Bug 1322938 - Basic implementation of HTMLDialogElement. (2e3b937f4) - Bug 1322938 - Emit close event when HTMLDialogElement.prototype.close() is called. (ef2cd8749) - Bug 1322938 - Update <dialog> element Web Platform Tests expected results. (a4011e724) - Bug 1322938 - Put <dialog> element behind preference. (b91b0c37e) - Bug 1322938 - Make the HTML tree builder aware of <dialog>. (25e85f99c) - Bug 1379728 part 1. Remove the double-definition of the 'close' event from EventNameList.h. (52bda2a82) - Issue #1348 - Part 1: Clean up input scope support for IMM32. (1672355a7) - Issue #1348 - Part 2: Teach IMEState about Private Browsing mode. (8ae047bbb) - Issue #1348 - Part 3: Set IS_PRIVATE input scope in private browsing. (d79cc5fb4) - Merge pull request #1347 from g4jc/html5_dialog (29bf28ca3) - Simplify value setting. (d429ac8a6) - Be more consistent about decoding IP addresses in PSM. (8198126c3) - Make copy of list before iterating over it. (51b1cd97a) - Handle missing base64 challenge in NegotiateAuth and NTLMAuth. (0186023f4) - Issue #1338 - Un-bust building of NSS after update to 3.48 on Linux. (936577621) - Update GTK clipboard handling (095a02f25) - Issue #1338 - Followup: certdb: propagate trust information if trust module is loaded afterwards, (f64e760ab) Official Pale-Moon changes since my last build: - Issue #1703 - Update UA overrides for Google and YouTube (832effab3) - Block Noveau NV96 mesa driver layers acceleration. (b7841e5cf) There are no new Official Basilisk changes since my last build. My changes since my last build: - ported mozilla upstream bug: Bug 1607443 - Fix some alias sets. r=tcampbell, a=lizzard (b8ab52794)