Leaderboard
Popular Content
Showing content with the highest reputation on 01/19/2019 in all areas
-
New build of basilisk/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20190119-082c0d218-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20190119-082c0d218-xpmod.7z diff: https://o.rths.cf/basilisk/UXP-xp-gitdiff-20181110.7z PM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.3.0a1.win32-git-20190119-082c0d218-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.3.0a1.win64-git-20190119-082c0d218-xpmod.7z Official repo changes since my last build: - Telemetry: Remove stubs and related code (5335681cd) - Remove unused telemetry timer from HTMLMediaElement.h (09a81ba9b) - Remove a pointless `switch` after telemetry cleanup (acf1406e0) - Make `AllowExperiments` return `false` as it is not useful without telemetry (633540464) - Merge pull request #929 from adeshkp/remove-telemetry-stubs (fb1d4c971) - [WebExAM] Use proper application name in WebExtension API error message. (c80c9cc40) - [PALEMOON] Clean up advanced prefs XUL (3e109856a) - [PALEMOON] Move Advanced prefs l10n strings to their proper place (41e07182f) - Add matching browser.newtab.choice pref to prevent error. (2ab82d7fc) - [PALEMOON] Add captive portal preference to the UI. (db15a3fdb) - Add preference for fully disabling HSTS. (3afb818f2) - [PALEMOON] Fix the option to disable HSTS. (1b9accd6f) - Improve toolbar icons for all DPIs (58f755254) - New cycle version bump (a20daf64b) - Add isIntersecting property to IntersectionObserverEntry. (f6ef8d8ca) - Fix check for HSTS when service is disabled. (a74b09347) - Merge pull request #931 from Ascrod/master (01ad6e745) - Rewrite IntersectionObserver list handling to be more robust. (ef8a5dca4) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (082c0d218)2 points
-
this is only a portion, there are some more missing parts. for details, you may do a WinMerge comparing with seamonkey's omni.ja\chrome\en-US\locale\en-US\ and borealis's omni.ja\chrome\en-US\locale\en-US\1 point
-
New build of post-deprecated basilisk/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.8, but some security patches can not be applied/ported due to source milestone differences between versions. Test binary: Win32 http://o.rths.cf/basilisk/basilisk55-win32-git-20190119-9c1bff848-xpmod.7z Win64 http://o.rths.cf/basilisk/basilisk55-win64-git-20190119-9c1bff848-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - update libaom to rev f4e775cf3753ec26109c8ced5621c565f53085b6 (without moz.build and aom_ports/aom_once.h) (69f3033c6) - update libaom to rev 9b1252eab0616d2c1f6d7990c6256441c0b6483f (without moz.build and aom_ports/aom_once.h) (bba80660d) - update libaom to rev c07e9d6ccf340843e8899e7da6b15a0893007bd5 (without moz.build and aom_ports/aom_once.h) (bfd0f4404) - update libaom to rev a1615ed01a112432825f231a1fa47295cff127b4 (without moz.build and aom_ports/aom_once.h) (abe401331) - update NSS to rev c8f7602ce9e6 with nss339-vc2013.diff applied (89623fdde) - import changes from wg9s seamonkey-2.49 patches: - Bug 1420865 - Don't check for CONTENT_MAY_CHANGE_TRANSFORM across layer trees. r=mstange, a=RyanVM - Bug 1466991 - Part 1: Factor out ShouldUseXBLScope. r=smaug, a=RyanVM - Bug 1376756 - gtk: while drawing nsTreeBodyFrame, fetch current row attributes for proper style rendering. r=karlt a=jorgk DONTBUILD - Bug 1465458 - Fix launching downloads without a file extension on Windows. r=mak, a=RyanVM - Bug 1470260 - Part 1: Ensure that 'this' stays alive for the duration of the TickRefreshDriver call. r=emilio, a=RyanVM - Bug 1470260 - Part 2: Make RefreshDriverTimer ref-counted and hold a strong ref on it on the stack when nsRefreshDriver::Tick can be reached. r=emilio, a=RyanVM - Bug 1469914 - Prevent the HAL from registering duplicate observers. r=froydnj, a=RyanVM - Bug 1472925 - Keep a strong reference to MediaStreamGraph from GraphDriver. r=padenot, a=RyanVM - Bug 468497: Inform the accessibility FocusManager when a XUL tree's view changes. r=MarcoZ a=jorgk DONTBUILD - Bug 1362303: Avoid crashes when dragging on macOS due to failed allocations of large shmem segments. r=glandium - Bug 1473161 - Add missing bound check in nsContentUtils::DataTransferItemToImage. r=nika, a=RyanVM - Bug 1456294 - Hook ImmAssociateContextEx. r=masayuki, a=RyanVM - Bug 1435319. r=valentin, a=RyanVM - Bug 1478679 - Fix memory leak in LCovCompartment. r=nbp, a=RyanVM - Bug 1468053 - Disable a workaround on macOS 10.14+ for an Apple bug described in bug 378645 involving popup windows that was fixed by Apple. r=mstange, a=RyanVM - Bug 1403945 - Add utility functions to recognize OS X 10.13. r=mstange, a=sledru - Bug 1468053 - Add nsCocoaFeatures::OnMojaveOrLater(). r=haik, a=RyanVM - Bug 1467889 - Adjust some uses of XPCOM strings. r=mrbkap, r=mstange, a=RyanVM - Bug 1474883 - Ensure D2D glyph cache is pruned after rendering 1000 transformed glyphs. r=bas, a=RyanVM - Bug 1450989 - Capture the action and target as part of the form submission creation. r=bz, a=RyanVM - Bug 1473113 - Defer initializing the MAR index until it's needed. r=rstrong, a=RyanVM - Bug 1467363 - Protect access to mTransparentSurface with a lock. r=rhunt, a=RyanVM - Bug 1404274 - Key Evaluation on the cloned JS objects. r=asuth, a=RyanVM - Bug 1480640 - Fix hazard in CopyingStructuredCloneReadCallback. r=baku, a=RyanVM - Bug 1480092 - Cherrypick rev 52add5896661d186dec284ed646a4b33b607d2c7. r=drno a=RyanVM - Bug 1466577 - Race condition in WebSocketChannel::StopSession. r=hurley a=dveditz - Bug 1461307 - Overwrite selection colors of widget which may be referred by IME via IM context with selection colors of GtkTextView. r=karlt, a=RyanVM - Bug 1480521 - Backport fixes from Bug 1479900. r=sfink, a=RyanVM - Bug 1469348 - Fix the problem of download file failed on Mac. r=paolo, a=RyanVM - Bug 1478575 - Unify CamerasChild shutdown paths. r=gcp, a=RyanVM - Bug 1461706 - Sync disabled state of number control regardless of appearance. r=jwatt, a=RyanVM - Bug 1485224 - Make best efforts to write a stack frame atomically. r=froydnj - Bug 1435212 - Add support for FFmpeg 4.0. r=bryce, a=jcristau - Bug 1512882 - Use Windows 7 search icon on Windows 8.x. r=IanN a=IanN - Bug 1496588: Avoid a UB in mozStorageService.cpp. r=froydnj - Bug 1500759 - Root parameter dictionaries in AesTask::Init(). r=keeler, a=lizzard (9c1bff848)1 point
-
DWM crashes with this code are not Aero Glass related. It probably happens when video adapter driver is disconnected and it randomly happens even without Aero Glass for a few last Win10 builds (but it is probably less noticable without Aero Glass which has some delay when it tries to generate minidump file on crash). About Fast Startup problem.. yes, there is some problem that Win10 behaves inconsistently between normal and fast startup. In fact, Win10 "Fast Startup" feature is one of the most buggy thing in Win10 and it is responsible for many "random" problems. For this reason, I disable it on every installation. As a workaround for current build, you could set this registry value: HKLM/SOFTWARE/Microsoft/Windows/DWM - DWORD GeometryCommand value set to 0x1cc.1 point
-
New Palemoon 27 Build! * This build is beyond official 27.9.4 build. 32bit https://o.rths.cf/palemoon/palemoon-27.9.1a1.win32-git-20190119-de2f91a7b-xpmod.7z 32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.1a1.win32-git-20190119-de2f91a7b-xpmod-sse.7z 32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.1a1.win32-git-20190119-de2f91a7b-xpmod-ia32.7z 64bit https://o.rths.cf/palemoon/palemoon-27.9.1a1.win64-git-20190119-de2f91a7b-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import changes from rmottola/Arctic-Fox: - Bug 1031152 - Part 2: Define a JSAPI test for the SavedFrame public API (5b391e61c) - add MOZ_OVVERRIDE and MOZ_FINAL taking from older upstream, since they were later removed. (45041af7f) - Bug 1129769 - Handle more kinds when resolving tracked type names. (76779d2bc) - Bug 1129769 - Followup: ignore indirect function calls from JSStreamWriter's use of std::ostream in hazard analysis. (df3fe0866) - Bug 1129780 - Report the youngest sampled frame's line number if it has optimization info. (46a5b92fc) - Bug 1131429 - Add a shell function to dump all of a function's tracked optimizations. (be91b86d0) - Bug 1136837 part 1 - Don't inline calls with incomplete type information for this or arguments. (0f88dc0f5) - Bug 1136837 part 2 - Improve |this| types when inlining after a CALLPROP/CALLELEM. (0f6e50f93) - Bug 1134638: 1. Add OperationName to MSimdBinaryBitwise (4100a5ff8) - Bug 1134638: 2. Inline some float32x4 binary arithmetic and bitwise operations (c7f3a22ea) - Bug 1134638: 3. Templatize inlineSimdBinary functions (39b6f6fab) - Bug 1134638: 4. Also test correctness of SIMD operations (8c9d75ed3) - Bug 1134638: 5. Add OperationName to MSimdUnaryArith; (69860fe64) - Bug 1134638: 6. Inline SIMD unary arithmetic operations (6a456e62e) - Bug 1134638: 7. Add spew for MSimd{Binary{Bitwise,Arith},Unary} (199320b8e) - Bug 1134638: 8. Inline SIMD conversions in Ion (6a06cc94c) - Bug 1047529 - Move caller field from MResumePoint to MBasicBlock. (2f2617ccd) - Revert "Bug 1047529 - Move caller field from MResumePoint to MBasicBlock." (b369b2f7d) - Bug 1120170 - part 1 - Change JSMSG_NOT_NONNULL_OBJECT message to accept an argument. (20c7374f3) - Bug 1120170 - part 2 - Self-host RegExp.prototype.flags. (469c3b324) - Bug 1135429 - Object.create shouldn't throw when its second argument is a primitive value. (a1b3545ba) - Bug 1047529 - Move caller field from MResumePoint to MBasicBlock. (7b00e8a79) - Bug 1134638: 9. Drive-by cleanup: FloatingTypePolicy can just have SPECIALIZATION_DATA (d5f86598c) (de2f91a7b)1 point
-
if you really want to use sm-2.49 langpack in borealis, there are some changes have to be done in sm langpack: - add this in install.rdf before last </Description> : <em:targetApplication> <Description> <em:id>{a3210b97-8e8a-4737-9aa0-aa0e607640b9}</em:id> <em:minVersion>1.0.0a1</em:minVersion> <em:maxVersion>1.0.0a1</em:maxVersion> </Description> </em:targetApplication> - copy chrome\<langcode>\locale\<langcode>\communicator\console\console.* to chrome\<langcode>\locale\<langcode>\global\ in sm langpack - copy datetimebox.dtd from borealis omni.ja to sm langpack chrome\<langcode>\locale\<langcode>\global\ and translate - copy communicator\consoleOverlay.dtd from borealis omni.ja to sm langpack chrome\<langcode>\locale\<langcode>\communicator\ and translate - modify sm langpack chrome\<langcode>\locale\<langcode>\global\findbar.dtd adding(and translate) these: <!ENTITY next.label "Next"> <!ENTITY next.accesskey "N"> <!ENTITY previous.label "Previous"> <!ENTITY previous.accesskey "P"> - modify sm langpack chrome\<langcode>\locale\<langcode>\navigator\tabbrowser.dtd adding(and translate) these: <!ENTITY bookmarkTab.label "Bookmark This Tab"> <!ENTITY bookmarkTab.accesskey "B"> then at least with won't stop working after applied langpack1 point
-
What do you people make of this? Didn't think anyone would actually bother to comment, but the author of Rufus himself did. Is anyone here who uses Vista on a regular basis actually concerned of the potential security implications? At least for me, regardless of the OS I use, whether that mitigation is enabled or not, it doesn't make a difference to me, because nothing ever gets on my PC without my explicit permission. I haven't used anti-virus software in years. To me, that's snake oil that only serves to give gullible people a false sense of security and slow the computer down and being downright annoying by deleting software that I actually want to run. It even happened to me once that I was compiling a program from source and NOD32 deleted the freshly compiled .exe right away! I was compiling a freaking game engine at the time... Windows Defender is the very first thing that gets turned off after Windows install. So, since this is primarily for the few Vista fans on this forum and that I don't really like programming and only ever bother with it if something I'd like to use is horribly broken or otherwise find some inconvenience that I'm able to fix, what do you think? Would you rather have a version that's potentially more secure or is the current fine? Honestly, my Vista image dates back to 2013, so it's possible that the bug with controls losing Aero appearance doesn't even occur when on a later patch level, but knowing MS, when their product goes out of mainstream support, they don't usually do any interesting updates. I guess I could compile both versions. I personally prefer the one that looks right.1 point
-
Well, it won't become less secure ... the risk, as always, is that someone will discover and exploit a vulnerability that was always there. So I'd keep an eye on security fixes for the nearest supported OS (probably Server 2008). Any vulnerabilities discovered in that are probably in XP also. Usually M$ gives an assessment of what it would take for an attacker to successfully exploit a new vulnerability. A lot of times it turns out to require physical access to the PC; most of us needn't worry about those (unless we're using XP machines at work!) If an over-the-network vulnerability is discovered, we could probably just block the affected port with Windows Firewall, unless it's something we really need.1 point
-
1 point