Leaderboard
Popular Content
Showing content with the highest reputation on 03/11/2023 in all areas
-
New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20230311-3219d2d-uxp-6f99b9744-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20230311-3219d2d-uxp-6f99b9744-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-20230311-3219d2d-uxp-6f99b9744-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-20230311-d849524bd-uxp-6f99b9744-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230311-d849524bd-uxp-6f99b9744-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230311-d849524bd-uxp-6f99b9744-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20230311-d849524bd-uxp-6f99b9744-xpmod.7z Official UXP changes picked since my last build: - Issue #1693 - Use scoped enums for IDBTransaction. (c920f32df) - Issue #2135 - Bug 1430303: Implement ShadowRoot.pointerLockElement (3dfffeaec) - Issue #2135 - Bug 1430305: Implement ShadowRoot.fullscreenElement (e286eb8ad) - Issue #2135 - Bug 1413102: Ensure Shadow DOM boundaries are dealt properly in event handling (24572438a) - Issue #2135 - Bug 1413102 (Follow-up): Ignore current target because of shadow DOM retargeting (1bb2009f6) - Issue #2135 - Bug 1323815: FocusEvent.relatedTarget should work consistently with MouseEvent.relatedTarget (1185cfe3f) - Issue #2135 - Bug 1438129: Remove ShadowRoot.applyAuthorStyles. (3350af82c) - Issue #2135 - Bug 1430301: Implement ShadowRoot.elementFromPoint/elementsFromPoint (e64aeea52) - Issue #2135 - Bug 1356496: Don't use nsIDOM* in ConfirmSelectionInBody (b2c77e5ed) - Issue #2135 - Bug 1066965: Make contentEditable and spellchecking to work in Shadow DOM (010db07bf) - Issue #2135 - Bug 1453789: Remove Element.createShadowRoot (45c179d01) - Issue #2135 - Bug 1410578: Make <link rel="stylesheet"> work in shadow trees (588c2154a) - Issue #2135 - Bug 1455891/Part 1: Improve StyleChildrenIterator (263b719ef) - Issue #2135 - Implement sequential focus navigation for shadow DOM (56193120c) - Issue #2135 - Bug 1518795: Properly track responsive content in a connected ShadowRoot (7b395189a) - Issue #2135 - Bug 1329877: Optimize AncestorFilter usage in lazy frame construction (7924a2f60) - Issue #2135 - Bug 1414692: Adopt shadow roots when adopting a shadow host across documents (b72ddcf65) - Issue #2135 - Bug 1393806/Part 1: Change nsNodeUtils cloning/adopting stuff to use an ErrorResult for errors (e65a864a3) - Issue #2135 - Bug 1393806/Part 2: Modify AdoptNodeIntoOwnerDoc to use the non-XPCOM version of document.AdoptNode (3062964d2) - Issue #2135 - Bug 1393806/Part 3: Change dom::ReparentWrapper to take an ErrorResult (9f0fb9c16) - Issue #2135 - Bug 1425864: Ensure printing documents which have shadow DOM works (015148fcc) - Issue #2135 - Bug 1419803: Use GetComposedDoc instead of GetUncomposedDoc in ContentEventHandler (70d493586) - Issue #2135 - Bug 1433669/Part 1: Remove dead function (2f9186959) - Issue #2135 - Bug 1433669/Part 2: Flush the document instead of the shell in ContentEventHandler (4d778226e) - Issue #2135 - Follow-up: Fix crash for passing nullptr as an argument to the aNodesWithProperties parameter (c194fbf6a) - Issue #2135 - Follow-up: Fix typo (9cb33ab84) - Issue #2046 - correct debug assert for intl_FormatRelativeTime() (3fb11e542) - Issue #2135 - Follow-up: Fix potential crash if shadow root is null (ad929c5dd) - Issue #2136 - Part 1: Implement CSS inset property (21d468ee6) - Issue #2136 - Part 2: Regenerate devtools CSS database (ae26d8a04) - Issue #2143 - Implement CSS env() Environment Variables (2b903a20b) - Issue #2135 - Follow-up: Ensure document is not null in nsImageLoadingContent::BindToTree (cfef3fa48) - Issue #2148 - Root the RegExpShared in RegExpMacroAssembler. (1f0df8f42) Official Pale-Moon changes picked since my last build: - [Pale-Moon] Set compatversion for hardcoded overrides to 102.0 (5a627b6ce) - [Pale-Moon] Issue #1915 - [SSUAO] Add override for Instagram (c8488397e) Official Basilisk changes picked since my last build: - Revert "[Basilisk] Fade out tab label on overflow instead of ellipsis" (15e3a38b5) My changes since my last build: - [Basilisk] ported PM version of tab caption fading to here (2a32b18f4) - [Basilisk] add tab caption fading to CtrlTab (f159e44b2) - [Pale-Moon] add tab caption fading to CtrlTab (5db2ae1aa) - Revert "revert last rev (7faa37b7) and revert rev b7e45308 and 9824659d instead." (1b1d672dc) - Revert "reverting rev 22dc363c and 233802c9 for now since I got a crash in destructor of RegExpShared." (6f99b9744) Update Notice: - You may delete file named icudt58l.dat inside program folder when updating from old releases. * 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.5 points
-
https://www.nirsoft.net/utils/chromepass.html chrome stored passwords can be retrieved with this little free portable utility.2 points
-
The original (Chinese) 360EE variants do NOT contain such a feature (nor do they contain the ability to export stored passwords) ...1 point
-
... If you happen to have the CTR extension installed in St52, it does offer that very same feature (plus a plethora of other customisations ): NB that the version fully compatible with St52 is "Classic Theme Restorer v1.7.8.2019.10.27" : https://github.com/Aris-t2/ClassicThemeRestorer/releases/download/1.7.8.2019/CTR_v1.7.8.2019.10.27.xpi You can always close a background/unfocused tab by placing your cursor on top of it (but not selecting it), followed by a middle mouse click (aka wheel-click, most mice today have it ); whether the close button is displayed in that tab or not makes no difference ...1 point
-
I use an excel file to save all of my passwords but this site is an exception because I don't have too much interest on it. can you tell me if the original chrome 360EE features the button to unveil the passwords or was it removed from the modified versions for whatever reason else.1 point
-
... Where do you plan to go, BTW? From my standpoint, this "project" will be discontinued once pukkandan abandons support for Python 3.8 altogether, which might very well be before its official EoS in 2024 ... IIRC, 3.7 is supported for a minority of users (on Vista and some Unixes where it can't be updated further) and 3.8 is still supported for the sake of Win7 users... Win7 support by most app authors/vendors will be waning as 2023 progresses (spearheaded by Google's decisions, no less), so the "inevitable" will happen... Anyone planning on backporting Python 3.9 to Vista SP2/XP SP3, please?1 point
-
... As others have hinted already, it may very well be an issue with your specific graphics card/its non-updated driver... Can you test that link you posted in latest Serpent 52? It works fine here via HTML5+WebGL (Adobe Flash hasn't been enabled): St52 doesn't block WebGL by default if your H/W can support it, so if you can't get it working in St52, "rebuild_8" will be moot for you... My 2c, of course ...1 point
-
All you need to do is delete the updater.node file.1 point
-
... But do take note that the password encryption used by Chromium forks uses data specific to the host system, so that utility can only decrypt and retrieve account credentials from the "machine" they were "created"/stored on, i.e. the browser profile isn't just enough to retrieve the credentials (unlike Firefox and forks) ... I was painfully hit by that when my laptop "died" (actually, its iGPU did) in the start of 2022; my portable 360EE versions (11/12/13/13.5), each with its separate profile, live on a USB HDD - when I connected that to a second laptop in my household (Win7SP1x64), the browsers+profiles launched fine, but I was unable to retrieve site account credentials with chromepass on that second machine ... So, I advise everyone reading this: Keep account credentials on a physical (piece of paper)/digital (USB drive) copy "unattached" to the machine you're currently working on ... FWIW, I retrieved 90% of my credentials from within a stored Serpent 52 profile ... In the end, my laptop was repaired and I retrieved (and backed up on paper) those missing 10% credentials (for sites running ONLY on a 360EE variant, not St52) via launching chromepass there ...1 point
-
1 point
-
APIs are changing rapidly. I never understood how the widgets work in Windows Vista/7, so I developed myself a script which gives you the weater of a specific city, so post here if you want it. I might upload it to github some day.1 point
-
I will upload a "rebuild_8" of my version that has WebGL ENABLED out-of-the-box. But you will have to PICK ONE OR THE OTHER, it is not advisable to run MY version and Humming Owl's versions side-by-side! Humming Owl's versions SAVE data to the Windows Registry permanently. Mine only uses the Windows Registry for temporary data storage - but it will "see" the PERMANENT data stored by Humming Owl's versions. Again, PICK ONE OR THE OTHER, it is not advisable to run both side-by-side - not even if one has been "exited" before the other is launched - Humming Owl's registry writes are PERMANENT. I will have a "rebuild_8" new thread later this weekend or so.1 point
-
No Sorry necessary at all @AstroSkipper as i can see (and appreciate) all your helpful input and contributions here! Well, coming from Thunderbird 2.0 (as i wrote here, pt 4.) i observerd this "alt row highlight" had gone in mailnews (at least per default), didn't find a reltated switch in the preferences, so i searched the web. Found this link where is described the solition with a userChrome.css: #threadTree treechildren::-moz-tree-row(odd) { -moz-appearance: none !important; background-color: rgb(232,232,232) !important; } which i've putten in the .\Profile folder of mailnews. Since this didn't show the desired result, i even added the preference toolkit.legacyUserProfileCustomizations.stylesheets set to true - but it didn't work neither. What was your way to get "alt row highlight" in mailnews?1 point
-
Why not just unplug the fan and underclock the CPU? (might require modding BIOS to avoid CPU fan error if it causes a system halt) You can use CrystalCPUID on 9x for this and there's plenty of software for DOS to slow down the CPU in it. My ThinkPad T42p has Intel 855PM chipset and it seems to be the latest one from Intel that is fully officially supported under 98.1 point
-
FantasyAcquiesce, probably has done what I have done, a time or two. It is easy to duplicate. First you install Vbemp, then you install whatever Win2k+ driver has a matching hardware vendor and device identification, and finally you reboot with your new driver. But you are not using the Win2k+ driver. You are using Vbemp. The registry changed the name of your device, to match the Win2k+ driver. But if you go to "Device Manager" > properties on the video device in "Display Adapters" > "Driver" tab > "Driver File Details", you will find the the Vbemp driver files are still listed. FantasyAcquiesce has even said, in that thread: The Intel video driver from RetroSystemRevival will not work. In fact, if you don't install Vbemp first, you'll end up with the default (16 color 640x480). I will gladly eat my words, if wrong. The only way to have evidence, the driver works, is to have a screenshot of the "Driver File Details". But I've installed drivers from 2k/XP, on Win98, and have seen the results; even the exact same driver we are talking about. It doesn't work. But, on the bright side, some of those Intel 8**G** chipset and video device drivers seem to support Win98. The device I pointed out had one. The issue is finding something without a fan. It seems anything that old, tends to have a fan.1 point
-
Good to hear that more people are able to make it work on older OS's, so that it won't be discontinued when I'm gone. That said, why version 2023.02.17? That was before a fix for a new throttling issue (see here). Also, you could make it start faster, when enabling "Lazy loading extractors" before compile from master: python devscripts/update-version.py python devscripts/make_lazy_extractors.py python pyinst.py1 point
-
Will depend on your graphics card. I do not need to change any flags to enable WebGL on any of my computers, I only need to not disable via the loader.ini.1 point
-
chrome://flags/#ignore-gpu-blocklist As pointed by @VistaLover for example.1 point
-
You will need delcert.exe mentioned by @mixit here -- https://msfn.org/board/topic/184135-arcticfoxienotheretoplaygames-360chrome-v135-build-2022/?do=findComment&comment=1233000 Then you will need rebase.exe and cab1.cab mentioned by @mixit here -- https://msfn.org/board/topic/184135-arcticfoxienotheretoplaygames-360chrome-v135-build-2022/?do=findComment&comment=1233344 chrome.dll was originally based at 0x10000000 i have been rebasing my chrome.dll at 0x10010000 (my last upload was "rebuild_7" and it was rebased at 0x3e1c0000 but I have since been using 0x10010000) I used Process Hacker 2.38.343 (I don't recall offhand, I think it was the last version to show System Information CPU, Memory, and I/O all on ONE PAGE). You can right-click 360chrome.exe and select Properties then go to a Memory tab to see where everything resides in memory by address. I was using two desktop computers (one on XP x86 and one on XP x64) and two laptop computers (both on XP x86). I ended up at 0x10010000 basically for no other reason then it worked on all four of my XP computers without conflicting with a "hooked .dll" (from a mouse-gesture program I run) that does or does not run on all four of those XP computers. If I recall, 0x10010000 was the smallest address I could rebase to that was higher than the original 0x10000000. It was my assumption at the time that selecting the smallest address possible increased chances of working on all four of those XP computers (because other members here were not having success with 0x3e1c0000).1 point
-
OK. I deleted the 360chrome key and another key called 360se6 (not sure where it came out though) problem still remains but I found out the issue I was using the 360 loader file (1814KB) from the application folder and not the main 360 loader (500KB) this is odd because with XP I use the same loader and there's no issue with it whatsoever1 point
-
https://github.com/abbodi1406/dotNetXP https://github.com/abbodi1406/vcredist/releases/tag/v0.35.01 point
-
Then your Windows Registry has been polluted with 360Chrome entries that should not be there. Step 1 - CLOSE 360Chrome Step 2 - verify in Task Manager that 360Chrome is NOT RUNNING Step 3 - launch regedit - 360Chrome must NOT BE RUNNING Step 4 - go to this section of your Windows Registry Step 5 - if you have any 360 or 360chrome keys between Software and where I have 7-Zip, DELETE THEM and REBOOT THE COMPUTER Step 6 - delete the entire 360Chrome folder, PROFILE AND ALL, and extract a brand new folder1 point
-
@Ryder252! As we all know, Windows XP is an old OS. I would try the .NET Framework Setup Verification Tool first. Strictly following the rule: old tool with old OS. Here is a link from archive.org as the original site is no longer available on Microsoft: https://web.archive.org/web/20170213203348/https://msdnshared.blob.core.windows.net/media/2016/10/netfx_setupverifier_new.zip1 point
-
New NewMoon 27 Build! 32bit https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20230311-33f0551ea5-xpmod.7z 32bit SSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20230311-33f0551ea5-xpmod-sse.7z 32bit noSSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20230311-33f0551ea5-xpmod-ia32.7z 64bit https://o.rthost.win/palemoon/palemoon-27.10.0.win64-git-20230311-33f0551ea5-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - lineContainer can be NULL in nsIFrame::InlinePrefISizeData::ForceBreak(), workaround it to fix crash when loading https://football.kulichki.net/england/ (40afff632d) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 599328 - Clicking a label shouldn't draw a focus ring if clicking the control wouldn't have. r=enndeakin (fe391aecaa) - Bug 1221947 - part 1: add BYTOUCH flag to nsIFocusManager, r=jaws,smaug IGNORE IDL (41b191e6f1) - Bug 1192573 - Require tablet-mode (Win10+) to show the on-screen keyboard. r=masayuki (9244e1d044) - Bug 1197722 - Respect Win10 pref about bringing up the touch keyboard outside of tablet mode. r=masayuki (00e20db670) - Bug 1210033 - Add on-screen keyboard diagnostic information to about:support. r=masayuki r=felipe (0101168557) - Bug 1211805 - rework keyboard detection for on-screen keyboard, r=jaws (d6eee8e170) - Bug 1221947 - part 2: add TOUCH cause to IME Handling and use it to avoid checking for a keyboard, r=masayuki (b39ad48728) - Bug 1221947 - part 3: pass touch information to focus manager in RenderFrameParent, r=kats (84bbf77326) - Bug 1229258: Implement dummy asmMergeWith/retargetWithOffset functions in none backend; r=h4writer (cb7c19dbfa) - Bug 1210577. Remove useless virtual keyword from ScrollFrameHelper::ComputeScrollClip. r=mstange (5c40b8bd98) - Bug 1177505 - Make all continuations fluid within non-bidi paragraphs. r=smontagu (6d7956c20f) - Bug 1216096: restore previous RTL caret behaviour by backout of bug 1164963, bug 1177505, and bug 1180417. r=jfkthame (11d974c609) - Bug 1157752 - In vertical writing modes, text-orientation:upright should force LTR directionality. r=smontagu (b8843ce65e) - Bug 1002466 - Use SK_ScalarNearlyZero instead of 0.0f to render dots r=mattwoodrow (79406a8ce9) - Bug 1214309 - nudge zero dash intervals to be non-zero under Skia. r=jmuizelaar (b781a0c63a) - Bug 1208234: Stop the null pointer crash. r=bas (e7fb7f56ad) - Bug 1202317. Bail out early if RequestRect is going to do redundant work. r=mstange (cc85741516) - Bug 1167026 - Avoid division by zero when flattening a bezier curve segment with equal control points. r=bas (11e036081a) - Bug 1166879. Avoid uninitialized read in FlattenBezier. r=mstange (893177de38) (f3497a0291) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1193786 - crash in mozilla::dom::Element::FindAttrValueIn, r=marcoz (1f03b9594f) - bug 1172516 - fix firing caret move events for proxied accessibles r=lsocks (6a62915a27) - Bug 582024 - ARIA active-descendant should work for ARIA owned elements, r=yzen (4fc7049fe1) - Bug 1212457 - crash at ARIARowAccessible::GroupPosition(), r=marcoz (dd058e3dcd) - bit of 1139049 (ae765adc6a) - Bug 1221542, bug 1221543 - crash in mozilla::a11y::DocAccessible::SeizeChild/PutChildrenBack, r=davidb (8a35b14523) - Bug 1105611 - HyperTextAccessible should set DOM range outside of pseudo elements r=surkov (19e2cf65cd) - Bug 1177765 - Add xmlroles for MathML. r=surkov (381201ae27) - Bug 1176683 - crash in mozilla::a11y::HyperTextAccessible::LandmarkRole() const, r=marcoz (f3fd977d35) - Bug 1176123 - Add NODE_CHILD_OF/NODE_PARENT_OF relations to mroot. r=surkov (36f08faa15) - Bug 1179483 - Fix crash in mozilla::a11y::HyperTextAccessible::RelationByType. r=MarcoZ (fec7fde5b3) - Bug 1177765 - Make nsIMathMLFrame expose the fence and separator properties of operators. r=karlt (91e45d9980) - Bug 1139709. Cache nsMathMLContainerFrame's intrinsic width. r=mats (ac40d07d89) - code style (c5f50fc0c3) - Bug 1226875 - Remove nsIFrame::GetLastChild(). r=mats (9b88566b77) - pointer style (6a5b9599f4) - Bug 1177093 - mathfont.properties does not need to be preprocessed after Bug 1000745 r=fred.wang (d114e285a1) - Bug 1224951 - Part 2: Fix -Wunreachable-code warnings in layout. r=dholbert (5854ee5e3e) - Bug 1141443 - Remove unused rpcns4 from OS_LIBS. r=mshal (1a5ccc985b) - bug 1218762 - proxy ia2Accessible::scrollTo{,Point}() r=davidb (db1db8e703) - Bug 1182208 - Add support for android scrolling and range accessibility actions. r=mfinkle r=yzen (29df38ee29) - Bug 1144516 - Remove offset of mozbrowser iframe. r=yzen (c7473a8feb) - Bug 1176292 - Send 'toggle-shade' control event to content on 3 finger triple tap. r=yzen (536932619a) - Bug 1182222 - Make Layerview support accessibility HTML navigation. r=yzen r=mfinkle (2beb411989) - Bug 1203697 - Add braille navigation. r=yzen r=mfinkle (d5a513e79e) - Bug 1209054 - Make 2 finger tap toggle pause speech. r=yzen (28bc8c16a6) - Bug 1214398 - Add highlight box to doc body if it is available and set z-index. r=yzen (9cca205849) - Bug 1182214 - Update highlight rect as you scroll. r=yzen (6d2738366a) - Bug 1182214 - Follow-up to fix Presentation.displayedAccessibles getter. r=me CLOSED TREE (6dd8ec3652) - Bug 1212528 - ensuring first seen document in ancestry is announced first. r=marcoz (fb8e9bc406) - Bug 1217038 - Remove for-each and legacy array comprehension from accessible/. r=yzen (810590b5d3) - Bug 1220860 - fixing an error with getting documentElement on AccessFu stop. r=eeejay (4a35fabc3d) - Bug 1169019 - Removed screenreader announcement from gecko. r=yzen (2b1732cddc) - Bug 1211122 - ensuring that we check position against an actual doc/dialog on doc load event. r=marcoz (78b7cc8a77) - Bug 1019432 - [AccessFu] Only capture explore by touch events in Android. r=yzen (eee4b09c72) - Bug 1182311 - Make 3 finger triple tap more reliable. r=yzen (7cf926a839) - Bug 1201146 - Introduce "Section" traversal rule. r=yzen (253d53ec8d) - Bug 1203283 - Introduce Android "Control" traversal rule. r=yzen (4d14ffa973) (e0e84a7434) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1216851 - Allow flattening of opacity when it contains text. r=roc (f62dead4b9) - Bug 1219833 - Respect composition underline color; r=masayuki nsTextFrame didn't use the composition underline color if the composition didn't have a foreground color defined. This patch makes it use the underline color if foreground color is not defined. (02bcedf5fb) - Bug 1211085 - Disable global reuse on b2gdroid r=khuey (a4bfc7c4e1) - Bug 1206817 - Take ownership of error reporting in the component loader. r=bz (d8b9b02dfb) (40ee015dc8) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1172382 - Enable AccessibleCaret on B2G. r=roc (f5c58c2798) - remove duplicated (8823cc4a43) - Bug 1219310 - part 1 - ask the prefs file for its size directly; r=njn (93073cbc5e) - Bug 1219310 - part 2 - keep track of how much pref file we have read; r=njn (6a2a10a8b1) - Bug 1213123 - Make Preferences::SetString accept char16ptr_t instead of char16_t*. r=froydnj (a895a36861) - Bug 1216901 - Make the FasterMake backend reticulate splines when moz.build or jar.mn files are modified. r=mshal (ed4ec93b18) - Bug 1219122 - Move webapprt.ini definition to moz.build. - Add corresponding webpprt files. (da6bc91b5c) - Bug 1219126 - Move greprefs.js definition in moz.build. r=mshal (52f404c935) - code style (1b1e543834) - Bug 1162690 - Remove malformed uri warning in nsURLParser::ParseURL r=mcmanus (8534fcebb7) - Bug 1163028 - URL: stop escaping [ and ] in path r=mcmanus (f2f3deec40) - Bug 1163030 - URL: stop escaping ` in query r=mcmanus (17d6c07640) - Bug 1191423 - Disallow illegal characters in cookies set via HTTP. r=jduell (b1786d140f) - Bug 1210235 - Skip package verification if pref out or no signature. The package would be treated unsigned. r=valentin (63870dd7ef) - Bug 1216062 - Notify OnStartSignedPackagedRequest with package identifier. r=valentin. (81a14af3db) - Bug 1214079 - Doom the package cache if the signature verification failed. r=valentin (83824c2d5d) - Bug 1178448 - Use imported CA in developer mode. r=keeler,valentin (b9cf64b477) - Bug 1216469 - Bypass verification for signed packages from trust origins. r=valentin (a36d0a6d2f) - Bug 1218284 - Match signed packages' with trust origin without suffix. r=valentin (45529dc7df) - Bug 412457 - should unescape hostname first, then perform IDNA r=mcmanus (23ebe47574) - Bug 1217316 - Remove for-each from netwerk/. r=jduell (8d0ca69e9e) - Bug 1208847 - Add telemetry to measure how often secure cookies are set from non-secure origins r=mcmanus (57ecf3651d) - Bug 1165267 - Part 1: Replace appId and inBrowser by originAttributes v2. r=honzab (7710301407) - Bug 1165267 - Fix downgrading issue by restoring appId and inBrowserElement columns v3. r=honzab (3e8b8e4dfb) - Bug 1221049 - Use originAttributes from TabContext. r=kanru (5eaebe3b28) - Bug 1197944 - Change pref so that the http auth dialog is presented for sub resources as well. r=jduell (e3a7e2a1a7) - Bug 1202421 - Rename the network.auth.allow-subresource-auth pref. r=michal (87e29e1fdf) - Bug 1213577 - Use OriginAttributes in nsHttpAuthManager, r=mcmanus (33d0a25ac4) - Bug 961049 - Part 1: Remove unused members and methods; r=baku (0f3e6de06b) (33f0551ea5)1 point
-
New build of post-deprecated Serpent/moebius for XP! * Notice: This repo will not be built on regular schedule, and changes are experimental as usual. ** Current moebius patch level should be on par with 52.9, but some security patches can not be applied/ported due to source milestone differences between versions. Test binary: Win32 http://o.rthost.win/basilisk/basilisk55-win32-git-20230311-bceff7b5b-xpmod.7z Win64 http://o.rthost.win/basilisk/basilisk55-win64-git-20230311-bceff7b5b-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - ported from UXP: Issue #1693 - Use scoped enums for IDBTransaction. (c920f32d) (e979bbad9) - ported from UXP: Issue #2135 - Bug 1430303: Implement ShadowRoot.pointerLockElement (3dfffeae) (a539f47bb) - ported from UXP: Issue #2135 - Bug 1430305: Implement ShadowRoot.fullscreenElement (e286eb8a) (85c7bdf68) - ported from UXP: Issue #2135 - Bug 1413102: Ensure Shadow DOM boundaries are dealt properly in event handling (24572438) (261bfcadc) - import from UXP: Issue #2135 - Bug 1413102 (Follow-up): Ignore current target because of shadow DOM retargeting (1bb2009f) (5a7b071dc) - import from UXP: Issue #2135 - Bug 1438129: Remove ShadowRoot.applyAuthorStyles. (3350af82) (5a041769a) - ported from UXP: Issue #2135 - Bug 1430301: Implement ShadowRoot.elementFromPoint/elementsFromPoint (e64aeea5) (b7a513b2a) - ported from UXP: Issue #2135 - Bug 1356496: Don't use nsIDOM* in ConfirmSelectionInBody (b2c77e5e) (9f1361118) - import from UXP: Issue #2135 - Bug 1066965: Make contentEditable and spellchecking to work in Shadow DOM (010db07b) (df33d59d4) - ported from UXP: Issue #2135 - Bug 1453789: Remove Element.createShadowRoot (45c179d0) (0d44f7d04) - ported from UXP: Issue #2135 - Bug 1410578: Make <link rel="stylesheet"> work in shadow trees (588c2154) (5ccbebc42) - ported from UXP: Issue #2135 - Bug 1455891/Part 1: Improve StyleChildrenIterator (263b719e) (7a99dec57) - ported from UXP: Issue #2135 - Implement sequential focus navigation for shadow DOM (56193120) (fa81bc7c9) - import from UXP: Issue #2135 - Bug 1518795: Properly track responsive content in a connected ShadowRoot (7b395189) (5b04b8ae3) - import from UXP: Issue #2135 - Bug 1329877: Optimize AncestorFilter usage in lazy frame construction (7924a2f6) (e951c9e2d) - import from UXP: Issue #2135 - Bug 1414692: Adopt shadow roots when adopting a shadow host across documents (b72ddcf6) (4ecb58c73) - import from UXP: Issue #2135 - Bug 1393806/Part 1: Change nsNodeUtils cloning/adopting stuff to use an ErrorResult for errors (e65a864a) (fbefa53b8) - import from UXP: Issue #2135 - Bug 1393806/Part 2: Modify AdoptNodeIntoOwnerDoc to use the non-XPCOM version of document.AdoptNode (3062964d) (30e05716d) - ported from UXP: Issue #2135 - Bug 1393806/Part 3: Change dom::ReparentWrapper to take an ErrorResult (9f0fb9c1) (2e76049ac) - import from UXP: Issue #2135 - Bug 1425864: Ensure printing documents which have shadow DOM works (015148fc) (e96983c69) - import from UXP: Issue #2135 - Bug 1419803: Use GetComposedDoc instead of GetUncomposedDoc in ContentEventHandler (70d49358) (31b47cb97) - import from UXP: Issue #2135 - Bug 1433669/Part 1: Remove dead function (2f918695) (e31a4854b) - ported from UXP: Issue #2135 - Bug 1433669/Part 2: Flush the document instead of the shell in ContentEventHandler (4d778226) (d1e5efcf8) - import from UXP: Issue #2135 - Follow-up: Fix crash for passing nullptr as an argument to the aNodesWithProperties parameter (c194fbf6) (b5e5cd188) - import from UXP: Issue #2046 - correct debug assert for intl_FormatRelativeTime() (3fb11e54) (56df8a677) - import from UXP: Issue #2135 - Follow-up: Fix potential crash if shadow root is null (ad929c5d) (ef8466fa6) - import from UXP: Issue #2136 - Part 1: Implement CSS inset property (21d468ee) (2d1a95825) - import from UXP: Issue #2136 - Part 2: Regenerate devtools CSS database (ae26d8a0) (e652e63b1) - import from UXP: Issue #2143 - Implement CSS env() Environment Variables (2b903a20) (44882a2d2) - import from UXP: Issue #2135 - Follow-up: Ensure document is not null in nsImageLoadingContent::BindToTree (cfef3fa4) (105fae466) - Revert "revert last rev (3ffaab07) and revert rev b1214c8d and 1d47bb34 instead." (20a127dae) - import from UXP: Issue #2148 - Root the RegExpShared in RegExpMacroAssembler. (1f0df8f4) (cb016b322) - Revert "reverting rev d5eb68a1 and 9535b71a for now since I got a crash in destructor of RegExpShared." (bceff7b5b)1 point
-
New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20230311-409cc309-uxp-6f99b9744-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20230311-409cc309-uxp-6f99b9744-xpmod.7z My changes since my last build: - [Navigator] ported PM version of tab caption fading to here (409cc309) source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom * Notice: the profile prefix (i.e. parent folder names) are also changed since 2020-08-15 build, you may rename their names before using new binaries when updating from builds before 2020-08-15. -- New build of HBL-UXP for XP! Test binary: IceDove-UXP(mail) https://o.rthost.win/hbl-uxp/icedove.win32-20230311-id-656ea98-uxp-6f99b9744-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20230311-id-656ea98-ia-93af9a0-uxp-6f99b9744-xpmod.7z My changes since my last build: - suite: ported PM version of tab caption fading to here (1b3cb632) source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild for UXP changes please see above.1 point
-
Do not copypasta text from other sites and make it a thread. Put the link to where you stole this info from. MSFN is in EU so we have the EU Copyright Directive to deal with.1 point
-
There is a special tool to check a .NET Framework installation called .NET Framework Setup Verification Tool. Download it from the internet! The more recent tool is now called Microsoft .NET Framework Repair Tool. Here is its download page: https://www.microsoft.com/en-us/download/details.aspx?id=301351 point
-
1 point
-
MWAV - eScan Antivirus Toolkit is an antivirus/antimalware offline scanner for a manual checking of the computer and cleaning if necessary. WiseVector StopX is an AI based antivirus program with a background guard, but its development has stopped, unfortunately So they are completely different and not easy to compare. You will find only a few tests of both tools in the internet. They are not as well known as the AV programs produced by big antivirus manufacturers. MWAV is a good tool, easy to handle and is updated on a regular base. I do trust it. For more information, follow this link to its English homepage: https://www.escanav.com/en/mwav-tools/download-free-antivirus-toolkit.asp If you are looking for an antivirus program with real-time protection under Windows XP, you can try Panda Dome. I wrote about this program in previous posts. In my system, I use both, Panda Dome and MWAV. A good combination, in my opinion.1 point
-
I haven't much info on this machine, but maybe the Xplore iX104C2 or iX104C3. It seems to come with the Intel 855GME. The audio is AC97. Up to 1Gb memory. 1Ghz or more. I also have no experience with the Intel 855GME. But it appears to support Win9x. Maybe not Win95? Edit: Nope. Watched a harddriver replacement video, and it has a fan. But it is a fairly small fan, and in an ideal location. Temps me to try the C4 at 1.4Ghz, with CPU throttling and a custom (larger) heatsink (Digikey). However, it would probably need USB for a keyboard. So no unicorn here.1 point
-
... For me, the first map there (Wifi Triangulation) loads (both map/satellite view) if I enable the geolocation API (in St52: geo.enabled;true - I had it toggled to false, for privacy concerns ); but the second map (IP Address based on ISP) still displays the quoted error in satellite view, map view loads a lightblue colour:1 point
-
Already aware. If you look at the releases discussed at MSFN, you will find that none of them contain this .dll. MULTIPLE .dll's have been removed during beta-stage telemetry-removal and testing. Several members contributed to that testing.1 point
-
... Just because things have gotten to be "how" they currently are "in IT world" doesn't mean I have to like or condone the way/speed with which they're "moving forward" (I use "forward" tentatively here; in many aspects, I feel it's just "progress" for the sake of "progress" itself ) ; so we have a new major version of Chrome/Firefox every 4 weeks; but why should web compatibility suffer so much, especially for those not willing to ride that high-speed train? Back in much saner times, there was a thing called "backwards compatibility" honoured among web developers; of course, the web itself then was a much nicer place, not the current JS-inundated abomination ... Rewind, please, to January 21st, 2010, when Mozilla Firefox 3.6 stable was released; no rapid-release-cycles at the time, the 3.6.x branch lasted all the way till March 13th, 2012, when 3.6.28 was released - some 26 months after the initial release; I was "there", and 95% of web pages would render in the same way between 3.6 and 3.6.28 ... FF to now and St52: You open a page today and it renders OK, revisit it next month, it may not load at all ... Nothing personal against you, UCyborg , I guess I simply needed to vent a little ...1 point
-
Exactly! Even the newest supported Chromium (109) is still going to work fine for a long time to come. Luckily Firefox is still supported, which is fantastic. There are many options for 7 at this moment, and while it may eventually end up where XP is at now, the future is much brighter right now for 7 users. (It's even brighter than that if you're on 10/11, but I'm staying with 7 for now because I prefer the old-school interface and the speed).1 point
-
Checking back in, this time from 7 x64. At this point there's nowhere to go but forward from here, as much as I hate to say it. Unless I'm on a PC so old that I need to use XP for full driver support, I'm pretty much sold on 7 for the foreseeable future. Though in some ways it was a regression from XP, it managed to improve in many ways that are important to me. Download speeds out of the box are MUCH better, so there's no serious need to keep a download manager around unless you are dead set on getting every last kilobyte your router is capable of routing. The kernel is significantly better too...besides being able to run a much wider range of browsers (and having much more modern options available), browsers seem to be much snappier and perform a lot better. I've currently settled on Waterfox G3 (Firefox 78-based). It's very fast, still has the now-deprecated Flash support, and just seems to be a good 'base' browser to put on a 7 build...and of course you can still download and experiment with other browsers too. I figure that I can download and try a newer version of Firefox, or a modern Chromium build, if a site gives me trouble in Waterfox. It seems 7 is on the road to taking the torch from XP as the new 'superstar' of legacy OSes and I predict that there will be many, MANY browser options for 7 users as time goes on. In general, it's good to be able to look at your options and see what works best. It was impressive to see the Mini Browser working so well in XP, but the aging XP kernel is being pushed to its limits, and of course the performance of Chromium 87 in Win7, both x86 and x64, just blows it out of the water. The fact that Chromium 87 even works in XP is amazing in itself, so I wasn't expecting miracles performance-wise.1 point