Leaderboard

Mathwiz wrote: >I second that motion. The change log is usually quite long and very technical; > hard to understand even for those of us who dabble in programming. > Putting it in a spoiler tag would let us refer to it if need be but save our scroll wheels if not... No, please not SPOILER! That tends to be hidden completely for old browsers, and not sure if also hindering page-search or archiving. Perhaps something else - "code"? But that increases the size yet more, using ultrawide Courier-fonts. Another...? (That said, I'd be surprised if RT changes anything at all only for reading convenience) But being a selfhelper, couldn't resist playing a bit now ;-) Tweak-1: This CSS filters all comments written by RT, then limits all single P-elements to a max height and if too long, shows a scrollbar: body.ipsApp article.ipsComment div[data-quotedata*='roytam1'] div.cPost_contentWrap p{ max-height: 400px !important; overflow-y: auto !important; } CSS-variations for example: remove author-requirement, or limit complete-comment height instead of single P-elements Tweak-2: This JAVASCRIPT (bookmarklet?) filters all comments written by RT, but (unlike above) takes the complete comment text. Then checks if the TEXT "- Bug " is contained more often than 8x. Only THOSE comments get limited with a scrollbar: var c="body.ipsApp article.ipsComment div[data-quotedata*='roytam1']"; var j, el, lg0, lg2, x, LIST=document.querySelectorAll(c); for (j=0; j < LIST.length; j++){ el=LIST[ j].querySelector("div[data-role='commentContent']"); lg0=el.textContent.length; lg2=el.textContent.replace(/- Bug /gi, '').length; x =(lg0 - lg2)/6; if (x > 8) { el.style.maxHeight='400px'; void(el.style.overflow='auto'); /* just for TESTING! Remove line: */ void(el.style.backgroundColor='yellow'); }} JS-variations: remove author requirement, choose another max-height, choose another TEXT, choose another hits-limit .

Thanks for the CSS! Works really well.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20220514-3219d2d-uxp-774750839-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20220514-3219d2d-uxp-774750839-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.rthost.win/basilisk/basilisk52-g4.8.win32-git-20220514-3219d2d-uxp-774750839-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.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20220514-d849524bd-uxp-774750839-xpmod.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20220514-d849524bd-uxp-774750839-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20220514-d849524bd-uxp-774750839-xpmod.7z Official UXP changes picked since my last build: - Issue #1891 - Fix ASAN and clang crashes on Linux, BSD and MacOS. Merge with the existing Solaris fix, by folding Solaris into the Linux/BSD section. Add Apple Silicon (ARM64) support. This should also address Issue #1884 by moving the offending code into assembly. (fd04893c3) - Issue #1509 - Invalidate previous result when datalist is changed. (046b81d06) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes picked since my last build: - gmp: replace preprocessor directives with AppConstants conditions (ef6b9353a) - pref: add CSS grid pref (297adbdb2) * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

According to my eye doctor, avoid using them! People "think" they are easier on the eyes in dark environments, they're actually damaging to your vision. Something about rods and cones. Eye doctor tried to explain it but I kinda phased him out because I don't use them anyway. And they way I see it, if they were "better" for your eyes, then you could buy health magazines and books where the text was white but the paper was dark.

What the heck is a "UOC patch" ? Disregard - found it -- https://msfn.org/board/topic/178306-the-uoc-patch-optimize-firefox-and-derivatives-for-old-hardware/ Did you alter any of the home PC fonts? ie, experiment with "emoji's" ?

The 1984 was quite a good one . What's your favourite chapter ?

Windows Update Error Codes If an error code occurs while accessing AU/WU/MU, it's helpful to understand the meaning of it. Here is a very comprehensive list of Windows Update Error Codes: http://inetexplorer.mvps.org/archive/wuc.htm Another list of these codes with more detailed descriptions is the "Complete List of Windows Update Error Codes" and can be found here: http://woshub.com/all-windows-update-error-codes/ Legacy Update also provides a list of Windows Update Error Codes. Here is the link: https://legacyupdate.net/errorcodes Cheers, AstroSkipper