Leaderboard
Popular Content
Showing content with the highest reputation on 07/15/2023 in all areas
-
New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20230715-3219d2d-uxp-787a64cf9-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20230715-3219d2d-uxp-787a64cf9-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-20230715-3219d2d-uxp-787a64cf9-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.7a1.win32-git-20230715-d849524bd-uxp-787a64cf9-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20230715-d849524bd-uxp-787a64cf9-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20230715-d849524bd-uxp-787a64cf9-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20230715-d849524bd-uxp-787a64cf9-xpmod.7z Official UXP changes picked since my last build: - No Issue - Fix debug builds on ARM Mac. mach_override used by the IO Poisoner used in debug mode is not support on ARM. https://bugzilla.mozilla.org/show_bug.cgi?id=1658385 (ffa0c4d86) - Issue #2268 - Fix Mac packaging by making the individual parts configurable. Add --with-macbundle-entitlement= to specify alternate entitlements or "none" Add --with-macbundle-type=hybrid to use the old DMG format. (eb2cca724) - Issue #2255 - Add support for Maybe<T&> https://bugzilla.mozilla.org/show_bug.cgi?id=1620568 Make Maybe<T>::emplace() work when T is const https://bugzilla.mozilla.org/show_bug.cgi?id=1335780 (efde4d468) - Issue #2255 - Use Maybe<> in the Performance API. (1f5eaee10) - Issue #2255 - Fix build bustage on Linux. Need #include <utility> to ensure std::forward is available. (323007ec3) - Issue #2271 - Separate cloning of native and interpreted functions (3eb7729d0) - Issue #2271 - Use declared names of self-hosted functions for cloning (76052fcda) No official Pale-Moon changes picked since my last build. Official Basilisk changes picked since my last build: - [Basilisk] Add pref to control history menu length. (11d652975) - [Basilisk] Follow-up: Don't show link items when pref is less than 1. (ab1a1e893) - [Basilisk] Follow-up: Throw errors on invalid values. (803bde238) - [Basilisk] Front-end fixes (748cac6e8) My changes picked since my last build: - [Basilisk] fix missing closing brace in function HistoryMenu from previous commits (cf35c4742) pdate Notice: - You may delete file named icudt*.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.8 points
-
Posting about Kaspersky is not off-topic here, as it's a security program which can still be used on Windows XP, which is the topic of this thread. Nobody here has the authority to ban the discussion of any program in any thread, unless it's off-topic for that thread. The risks of using Kaspersky are now well known, and should be discussed, but only on a technical basis, not concerning the software's origins, which quickly descends into political rows, which are not allowed here in technical threads. It's up to individuals to make the choice as to whether to still use programs like Kaspersky. Helping people make that choice is what these discussions are all about.6 points
-
Oh noes, not again. https://msfn.org/board/topic/184730-antimalware-firewall-and-other-security-programs-for-windows-xp-working-in-2023-and-hopefully-beyond/page/18/#comment-1247635 That particular CVE is definitely not the reason why a number of governments issued warnings and prohibitions about the use of that antivirus. That one, at the most, can be used to de-anonymize the user in very specific cases (i.e. after a phishing attempt succeeded). The actual reasons why must (should) be much, much worse (and have not been disclosed), the "original" ban about its use on US government hardware is 2017 (two years before the mentioned CVE), other bans and warnings are 2018 (one year before) and 2022 (three years later): https://en.wikipedia.org/wiki/Kaspersky_bans_and_allegations_of_Russian_government_ties jaclaz4 points
-
4 points
-
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-20230715-80e0e6c0d-xpmod.7z Win64 http://o.rthost.win/basilisk/basilisk55-win64-git-20230715-80e0e6c0d-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - import from UXP: No Issue - Fix debug builds on ARM Mac. mach_override used by the IO Poisoner used in debug mode is not support on ARM. https://bugzilla.mozilla.org/show_bug.cgi?id=1658385 (ffa0c4d8) (b64f39991) - import from UXP: Issue #2268 - Fix Mac packaging by making the individual parts configurable. Add --with-macbundle-entitlement= to specify alternate entitlements or "none" Add --with-macbundle-type=hybrid to use the old DMG format. (eb2cca72) (a18a245ab) - ported from UXP: Issue #2255 - Add support for Maybe<T&> https://bugzilla.mozilla.org/show_bug.cgi?id=1620568 (77c610e08) - ported from UXP: Issue #2255 - Use Maybe<> in the Performance API. (1f5eaee1) (71da512f5) - import from UXP: Issue #2255 - Fix build bustage on Linux. Need #include <utility> to ensure std::forward is available. (323007ec) (bf4b9f978) - import from UXP: Issue #2271 - Separate cloning of native and interpreted functions (3eb7729d) (4d9448be9) - import from UXP: Issue #2271 - Use declared names of self-hosted functions for cloning (76052fcd) (29940b325) - import from UXP: - [Basilisk] Add pref to control history menu length. (11d65297) - [Basilisk] Follow-up: Don't show link items when pref is less than 1. (ab1a1e89) - [Basilisk] Follow-up: Throw errors on invalid values. (803bde23) - [Basilisk] Front-end fixes (748cac6e) (817466305) - js: fix error reporting crash (80e0e6c0d)4 points
-
I have not been following the thread but did see a very tiny portion of all of the Kaspersky talks. I only hereby submit that the thread remain informative and unbiased and non-political. My "two cents" in regards to making 2023 decisions based on 2017 "bans" would be this - how many government agencies have banned XP and should we be using that as a metric to ban XP on our personal computers? My answer would be a resounding NO.3 points
-
Thank you for the attention, sorry, I'll not go offtopic. I'm a new member, I obvioulsy don't know how everything works here, but I find it odd why would you want me to, at the same time implying @UCyborg's posts are off-topic. I will post my findings with XP. when I'm finished with them, don't worry. Again, thank you for the attention! I read through this thread and became a huge fan of@AstroSkipper , for his hard work and findings. I saw numerous times you zealously suggest a very dangerous software named "Kaspersky". I fail to get why. Why would you want to harm the others? Isn't it against the rules to advise harmful soft, when it's publicly known, declared by the US officials, and explained to you personally multiple times. And again, posting about Kaspersky is also indeed offtopic, since it's been removed by the OP, due to the discovered infection risks and harm it brings. https://nvd.nist.gov/vuln/detail/CVE-2019-82863 points
-
Agreed, and can relate with you on this. 🙂 Thank you so much roytam1 for your work, and all kudos go to him!2 points
-
I did read it, yes. But I have also read dozens of articles informing the user how to remove the usage of unique identifiers. It is public knowledge and to hide that while shouting about "bans" is a bit BIASED in my view. I myself take that route. I remove/disable telemetry before using Win10. I remove/disable telemetry before using 360Chrome. Even an HONEST Firefox user will tell you that Firefox collects telemetry if the end user does not remove/disable it. An antivirus's sole role is to prevent viruses. The effectiveness of that and that alone (and ability to run on XP) should dictate whether it is discussed in this thread. PLUS how to disable telemetry. Software collecting telemetry is "much ado about nothing" (many do this in the guise of "improving their product"). But an informed user that is NOT showed how to disable telemetry (or even hides that it can be disabled) is also pushing an agenda. There are two sides to this coin. And both sides are equally legit, or so it seems to me. I've said all I need to say, I trust the MSFN Reader is intelligent and above average of a conumser or they would not be here in the first place. I trust them to make the informed decision.2 points
-
I don't think any US Government Department/Agency has publicly "banned" XP. But I can find several articles stating that they have abandoned XP in favor of 10 -- https://www.minitool.com/news/defense-finally-abandon-xp-for-windows-10.html Does that mean that all XP-related threads here at MSFN should "move on"? Again, a resounding NO. I only site this "correlation" (if it can be seen as such) in the sense that if we can PROVE that Kaspersky of 2023 is NOT THE SAME as the Kaspersky of 2017, then let the reader make the informed decision on whether to use it or not. In the world of IT and computers, almost ALL articles in 2017 no longer apply in 2023 - unsure if this is the case for Kaspersky.2 points
-
I do not recognize the OP’s authority to declare Kaspersky “not an option for Windows XP.” For XP users with SSE-only processors, the alternative to Kaspersky will soon be no real-time protection at all. I do not own such hardware myself, nor have I ever used Kaspersky. If others prefer not to use Kaspersky for political reasons, that’s fine with me.2 points
-
I understand your desire to focus on MyPal rather than having your time split between two browsers, but if you ever have the desire to continue Centaury development you have my full permission to do so.2 points
-
55.0 is back, as usual thanks to Roy for all his work. And as a bonus, formhistory and passwords are also functioning properly. :)2 points
-
... Indeed it has been! Many thanks for working overtime this Saturday morning ; hopefully, the rest of your weekend will go by trouble-free ... Cheers!2 points
-
Running the most recent, corrected version of Serpent 55 (2023-07-14) (rev 80e0e6c0d), basilisk.exe is starting and running fine again as it should. No further crashes observed. Big thanks to @roytam1 for the quick fix! Cheers, AstroSkipper2 points
-
New regular/weekly KM-Goanna release: https://o.rthost.win/kmeleon/KM76.4.7-Goanna-20230715.7z Changelog: Out-of-tree changes: * update Goanna3 to git 7e7ba08548..3850bfcb24: - revert binding xml preprocessing settings from previous commit (585686d345) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1207790 - Fix sandbox build for older Linux distributions. r=gdestuynder (33726f14d6) - Bug 1157864 - chromium sandbox: Fix compilation for systems without <sys/cdefs.h>. r=jld (19789c8f28) - Bug 1181704 - Import chromium SafeSPrintf. r=bobowen (c8f2f34098) - Bug 1196403 - Apply crbug/522201 to support Windows 10 build 10525. r=bobowen (ee9862b408) - Bug 1200336: Apply fix for Chromium issue 482784 for sandbox bug when built with VS2015. r=tabraldes (7f4cf9640b) - Bug 1150765 - Add sandbox rules to allow hardware rendering of OpenGL on Mac. r=smichaud (e23a3d3e89) - Bug 1153809 - Loosen Mac content process sandbox rules for NVidia and Intel HD 3000 graphics hardware. r=areinald (9a3a1fa6ea) - Bug 1229804: Use the correct string length in Windows sandbox logging. r=tabraldes (6a8cb035ed) - Bug 1181704 - Use chromium SafeSPrintf for sandbox logging. r=gdestuynder r=glandium (cff9ae432b) - crash reporter (009341774b) - Bug 1168555 - Work around Nuwa not always being single-threaded when a normal content process is. r=kang (b858b1fd62) - Bug 1199413 - Fix MOZ_DISABLE_GMP_SANDBOX so it disables all the sandboxing. r=kang (49125e07be) - Bug 1176085 - Fix second/nanosecond confusion in Linux sandbox start error case. r=kang (701181c7d2) - Bug 1199481 - Complain more when entering sandboxing code as root. r=kang (baf7b24675) - Bug 1215303 - Part 1 - add permissive mode r=jld (e8237859ac) - Bug 1215303 - Part 2 - automatically enable broker when in permissive mode r=jld (9636c8a956) - Bug 1222500 - Handle unexpected thread creation better on desktop Linux. r=gdestuynder (58e2f81f96) - Bug 1131227 - Make the about:certerror Unknown Issuer string mention missing intermediates and unimported roots. r=keeler (29ae92e655) - Bug 443811 - Use long date format for cert date output. r=keeler (50a31e099c) - namespace (10ccb72736) - Bug 1225682 - Don't use nsAuto{,C}String as class member variables in security/manager/. r=keeler (24d10b66f6) - Bug 1110935 - Part 1 - Assert we're on the main thread on public methods. r=keeler (b9b2b52bf2) - Bug 1110935 - Part 2 - Remove ReentrantMonitor and ReentrantMonitorAutoEnter uses. r=keeler (3fee4d4653) - Bug 1110935 - Part 3 - Remove now unnecessary temp variables. r=keeler (f81461993a) - Bug 1168635 - Add an XPCOM interface to allow RC4. r=keeler (dac5f75e75) - Bug 1136301 - Null check for mCert->slot added in destructorSafeDestroyNSSReference & MarkForPermDeletion. Formatting update in MarkForPermDeletion. r=keeler (daaaf2db22) - Bug 1168048 - Avoid potential null-pointer dereferencing in nsNSSCertificateDB r=keeler (c511046073) - Bug 1224121 - change getRelativeRuleLine to return 0 for line-less rules; r=heycam (7cef25806d) - Bug 1216234 - add inIDOMUtils.getCSSPseudoElementNames; r=heycam,pbrosset (1c94ca86b4) - Bug 1146114 - Make assertion checking additional leading in ruby frame non-crash. r=dholbert (326d82db79) - Bug 1052924 followup - Move the XXX comment to the right field. DONTBUILD (481cb50d0d) - Bug 1136521 - Don't try to use the ascent when placing a frame whose block-direction doesn't match the line's. r=smontagu (eb01f6aa1a) - Bug 1138353 - Correct the directionality of vertical-align dimensions in cases where line- and flow-relative coordinate directions differ. r=smontagu (6e51f4be05) - Bug 1133945 - Fix behavior of vertical-align with a specified length, relative to dominant centered baseline in vertical mode. r=smontagu (a2e611f978) - Bug 1146117 - Downgrade the assertion in FindNearestRubyBaseAncestor to warning. r=dbaron (db29a321f4) - Bug 1191185 - Simplify nsHypotheticalBox, eliminating obsolete/redundant fields, and rename to nsHypotheticalPosition. r=dholbert (3741b6aa49) - Bug 1227099 - [css-grid] Grid container block-size should include a grid-row-gap between each row. r=dholbert (35eed9d00b) - Bug 1225368 - [css-grid] Make CollectGrowable() deal with frozen tracks; i.e. subtract their base size but don't collect them since they aren't growable. r=dholbert (073964a857) - Bug 1224634 - [css-grid] Make grid items shrink-wrap when reflowing them, unless they have justify-self:stretch. r=dholbert (070c2cf6a9) - Bug 1176793 part 1 - [css-grid] Implement margin:auto for grid items. r=dholbert (ff89b80fc2) - Bug 1176793 part 2 - [css-grid] Reftests for margin:auto on grid items. (fe9367e7ca) - Bug 1229999 - [css-grid] Clamp auto-placed lines to where kMaxLine is in the translated grid. r=dholbert (576d9a8384) - Bug 1151243 part 1 - Replace three bool params for nsAbsoluteContainingBlock::Reflow with a flag param (idempotent patch). r=dholbert (7303bb9468) - Bug 978212 - [css-grid] Resolved value of grid-template-{columns,rows} in px units. r=mat (fe4b886917) - Bug 1151243 part 2 - [css-grid] Add a eIsGridContainerCB flag for nsAbsoluteContainingBlock::Reflow to trigger Grid specific code (rather than checking GetType()). r=dholbert (2f5f857b16) - Bug 1215099 part 1 - [css-grid] Backout bug 1206703. r=dholbert (b6af6389ce) - Bug 1123299 - Allow <input type=number> to be displayed in vertical writing mode; but keep the spinner arrows arranged as for horizontal writing mode. r=dholbert (2a2e17ce76) - (no bug) Fix typo in grid style-struct comment: s/grid-columns-rows/grid-template-rows/. No review, DONTBUILD (f362946aed) - fix namespace (70ec283c08) - Bug 1224251 patch 1 - Add reftests. r=mattwoodrow (4f5eed4d0c) - Bug 1224251 patch 2 - Add nsChangeHint_UpdateUsesOpacity to say when opacity changes between 1 and non-1. r=xidorn (0cec051688) - Bug 1224251 patch 3 - Return nsChangeHint_UpdateUsesOpacity when opacity changes between 1 and non-1. r=xidorn (acf5f3514c) - Bug 1224251 patch 4 - Convert UpdateOpacityLayer to RepaintFrame when changing opacity between 1 and non-1 on table parts. r=mattwoodrow (3101e06481) - Tweak a couple of comments; no bug. (DONTBUILD) (6b7d8486ad) - Bug 1219534 - Remove unused nsStyleContext::SetStyle##name_ methods. r=dholbert (4c032b5914) - (no bug) Fix typo in nsStyleContext.h (s/currenlty/currently/). Comment-only, DONTBUILD (3864f8194b) - Bug 1208901 - Fix a typo in nsStyleClipPath::nsStyleClipPath; r=heycam (df5c3b59a6) - Bug 1227766 patch 3 - Make will-change cause creation of a containing block for fixed and absolutely positioned elements when needed. r=dholbert (09c59e07f1) - Bug 1229278 - Fix dynamic changes to text-emphasis-style. r=dbaron (ab0c450f14) - Bug 1159729 - Reftest to check that text decoration is properly offset when needed. r=smontagu (b93bb0ca41) - Bug 196292 - Make table inside align=left reset alignment just like for align=center and align=right. r=bz (3b45a62477) - Bug 1227917 - Update |disp| after we've (potentially) cloned the Display struct so that subsequent tests of 'display' use the new value. r=jfkthame (d3216e7aad) - Bug 1155766 - Fix a bad assertion r=dbaron (d6744220f4) - Bug 1167589 - Mark the members of CSSParsingEnvironment as MOZ_UNSAFE_REF. r=dbaron (ebb9729549) - Bug 1228542 - Resetting AuthorStyleSheets. r=bz (31b27e491d) - Use nsContentUtils::GenerateUUIDInPlace() in nsIDocument::GenerateDocumentId(), no bug (642138ebac) - Bug 1226443 P2 Make service worker fetch and functional events used scheduled timer updates. r=ehsan (a4fc5a9275) - Bug 1227015 P1 Create ServiceWorkerScriptJobBase as parent class to register and install jobs. r=ehsan (214dda4e7d) - Bug 1226443 P1 Add a timer based mechanism for firing service worker updates. r=ehsan (f2a9eae9d2) - Bug 1229052 - Add a telemetry histogram to gather data on the number of top-level pages with scroll-linked positioning effects. r=vladan (6844bfaa2b) - Bug 1229052 - Log a warning when we detect a scroll-linked effect based on the scroll event. r=roc (da8dd5cff2) - bug 1215657 - make AccessibleWrap::get_accFocus work with proxied accessibles (02bfa582d6) - Bug 1227285 part 1 - Add a nsHTMLReflowState ctor flag to request shrink-wrap behavior. r=dholbert (da92253664) - Bug 1227285 part 2 - [css-grid] Request shrink-wrap behavior when doing a measuring reflow to figure out a grid item's block-size. r=dholbert (6bfcf381fe) - Bug 1227285 part 3 - [css-grid] Reftests for testing minmax(min-content,max-content) track sizing with grid item with %-sized descendants. (61b769d0d2) - No bug - [css-grid] Add a small fuzz factor to make this reftest pass on Windows. r=me (3c51c91220) - Bug 1173689: allow column sets in an orthogonal writing mode to their container to expand in the container's block direction, r=roc (88aa32efd9) - Bug 1209994. Take block-wrapper path only for blocks that are wrappers. r=bz (ecb4ae8d7e) - Bug 1191109 - Clean up use of writing-modes in GetHypotheticalBoxContainer, eliminating a redundant ConvertTo call. r=dholbert (f58d0d63c4) - Bug 1183439 - Update the wording of a few assertions to reflect logical-coordinate conversion. r=dholbert (8aacb0f89d) - Bug 1233276 - Make css::Declaration::List more useful again, given that it degraded a bit in bug 978833 (/ bug 1221436). r=heycam (1efda568e7) - Bug 1167665 - Mark css::Loader::mDocument as MOZ_NON_OWNING_REF. r=dbaron (f4d4f4ed1d) - Bug 621596 - Don't assert when a percentage base value overflows to become negative, when getting the computed style of a property that rejects negative values. r=bzbarsky (6076ce7cb6) - Bug 622314 - Add crashtest. (f1d64b943c) - Bug 1230613 - Long-press to trigger text selection should vibrate, r=snorp (f35f37336e) - Bug 1230582 - Always show caret even if input is empty on Fennec. f=capella, r=roc (6cf1258232) - Bug 1183085 - Correct argument name for BuildContainerLayerFor; r=roc (0fd119efd1) - Bug 1183085 - Correct a typo in FrameLayerBuilder.h; r=roc (1fb9a583ed) - Comment typo fix; no bug. (DONTBUILD) (27d7270052) - Bug 1211858 - Add a hint for the Restyle label when the id is unavailable. r=roc,benwa (8eb99a4b45) - bug 1218596 - remove nsPSMInitPanic and other unnecessary things from nsNSSComponent r=Cykesiopka r=jcj (a986e73f0b) - bug 1220223 - don't load PKCS11 modules in safe mode r=mgoodwin r=bsmedberg (5e071955b0) - Bug 921907 - Enable OCSP must-staple. r=keeler (448661431f) - Bug 1215795 - Fix documentation in nsIWeakCryptoOverride.idl. r=keeler IGNORE IDL (3cf051737c) - bug 1222179 - remove unnecessary observation topics in nsNSSComponent r=Cykesiopka (2eaa16d860) - bug 986956 - only ever initialize NSS once per process r=Cykesiopka r=mgoodwin (efdec10cbb) - Bug 1224875 - Enable TLS extended master secret. r=keeler (8f56d54ec1) - Bug 1145893 - Shutdown nsNSSComponent background threads during xpcom-shutdown. r=keeler, a=me (5d513b930d) - namespace (bf40a8f575) - Bug 1224951 - Part 1: Fix nsPresContext::SizeOfExcludingThis() size calculation. r=dholbert (530a54e15d) - Bug 1227666 - Insure that cached plugin geometry configuration cached in ShadowLayerForwarder gets cleared when we reflow and new content has no plugins. r=roc (a44fbce70e) - Bug 1140625 - Part 1: Add recursive call in GetFrameForNodeOffset. r=roc (0b7535cf7b) - Bug 1140625 - Recursive call GetFrameForNodeOffset if text node has no frame. r=roc (9198ab6a20) - Bug 1140625 - Part 3: Fix a bug in bug414526 so we can reopen the test. r=roc (cbe0d3577d) - Bug 1140625 - Part 4: Fix scroll_selection_into_view test to make its function remain. r=roc (97ca749e63) (cbf860dd80) - nsPrinterEnumeratorWin: replace while-loop with for-loop, this may fix race-condition on generating printer name list (dc4029b3f8) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1228921 - Write nsChangeHint constants using left shifts. r=xidorn (cc7702d508) - Bug 1228921 patch 2 - Fix nsRestyleHint constants to match the same style. r=xidorn (1ec516e7fb) - Bug 1077085 - Insure puppet widgets don't skip sending resize notifications to the view manager when the user navigates through history items. r=tn (6ebc5e2ec4) - Bug 1188665 - Make nsIDOMWindowUtils.disableDialogs() disable onbeforeunload dialogs. r=bz (c1832372ff) - fix misspatch in Bug 1224464 patch 2 (710f8de1ae) - Bug 1175192. Consistently allow identifiers to start with -- in the CSS parser. r=heycam (5c4ced2937) - Bug 1220903 - Allow style to access chrome-only properties if it is loaded via chrome protocol. r=bz (155b2099cc) - Bug 1217643 part 0: Add reftests for -webkit-gradient() expressions. r=heycam (adc23dade1) - Bug 1217643 part 1: Add partial support for parsing CSS -webkit-gradient expressions (if webkit prefix support is enabled). r=heycam (715c0364b2) - Bug 1217643 part 2: Represent parsed CSS -webkit-gradient(linear, ...) expressions internally as parsed versions of more modern syntax. r=heycam (2f06829293) - Bug 1217643 part 3: Represent parsed CSS -webkit-gradient(radial, ...) expressions internally as parsed versions of more modern syntax. r=heycam (f2903d9cec) - Bug 1228051 - Remove PR_snprintf calls in nsCSSParser.cpp's CSSParserImpl::ParseColor. r=dholbert (f3845e9bac) - Bug 1221823 patch 1 - Use rvalue-reference and Move rather than just comments to show behavior of nsCSSKeyframeRule constructor. r=xidorn (07196fd12f) - Bug 1221823 patch 2 - Use already_AddRefed<Declaration>&& as parameter to nsCSSKeyframeRule constructor to avoid extra reference count cycle. r=xidorn (c4b441fc83) - Bug 1232596 - initialize variable changed = false, flagged by Coverity. r=dbaron (1e662aea38) - (no bug) Fix typo (repeated word) in comment. comment-only, no review, DONTBUILD (dbb43c2638) - Bug 1213842 - :lang() should not fall back to HTTP headers if empty lang attribute is specified; r=bz (6992d47faa) - bits of Bug 1202744 - Overlapping software home buttons r=snorp (5913a799f1) - Bug 1171368 - Fix -Wunreachable-code-break warning in layout/style/nsCSSRuleProcessor.cpp. r=dholbert (2d006c9e7e) - Bug 1202512 - Part 3: Restyle elements with attribute/state changes if we find a conditionally restyled ancestor while selector matching up the tree. r=bzbarsky (ea671029bb) - Bug 1202512 - Part 4: Reftests. r=bzbarsky (418aae6b65) - Bug 1097242 - Make sure contenteditable -moz-user-select styles can be overridden by web pages; r=dbaron (c1a0172841) - Bug 1166969 - Video element in the video document shouldn't be selected. r=roc (fb9621837b) - Bug 1169901 - View source menu covers full height. r=heycam (6225279b1a) - Bug 1230508 - Always compute position to fixed for top layer elements for now. r=dbaron (55475be4f2) - Bug 1230508 - Always compute position to fixed for top layer elements for now. r=dbaron (10a918d358) - Bug 1216362 - Measure nsCSSSelector::mAttrList. r=erahm (110a191205) - Bug 1156392 - Remove an ifdef condition that we don't need any more. r=tn (84f9f7748d) - Bug 1215957 - Start at the end of the explicit grid also when matching plain negative number lines. r=dholbert (21b56f9b66) - Bug 1226697 part 1 - [css-grid] Fix off-by-one error when counting lines in reverse. r=dholbert (b8293a7c4b) - Bug 1211260 - Implement the new Grid Placement Conflict Handling: "If the placement for a grid item contains two lines, and the start line is further end-ward than the end line, swap the two lines." r=dholbert (a740de6866) - Bug 1211260 - [css-grid] Follow-up: address a code readability nit that I missed. r=dholbert (d98517d455) - Bug 1215099 part 2 - [css-grid] An empty grid should still have one explicit grid line in each axis. r=dholbert (8b80702949) - Bug 1230695 - [css-grid] abs.pos. child spanning from an 'auto' start position to an end line should end on the start side of the gutter. r=dholbert (02dfb8610a) - Bug 1229145 - [css-grid] Account for start margin when calculating border box offset for align-self/justify-self:center. r=dholbert (f4b030f775) - Bug 1224634 - [css-grid] Tweak a few tests to account for correct 'justify-self' behavior. (2fa37ac545) - Bug 1229145 - [css-grid] Adjust align-self/justify-self:center reference rendering to reflect the corrected margin calculations. (c95ab49645) - Bug 1225118 - [css-grid] Deal with nscoord overflow when applying [align|justify]-self:stretch. r=dholbert (9db2a3b1ca) - Bug 1225118 - Crashtest. (71d85472da) - Bug 1227216. Part 1: Only draw surface on inset box shadows if dest and src are equal sizes. r=mstange (6adb32966c) - Bug 1227216. Part 2: Fallback to blur destination rect if a large shadow offset occurs. r=mstange (bfad4ecb03) - Bug 1178575 - tests. (519597225f) - Bug 1212823 - Use correct coordinate space for box-shadow native rect when doing themed drawing. r=roc (25ab30fa1a) - Bug 1229165 - [css-grid] Apply min/max-width/height properties to clamp block-size of auto-height grid containers. r=dholbert (eaf4864e88) - Bug 1228984 - [css-grid] Auto-placement into columns missed some unoccupied span-1 column slots. r=dholbert (e6bbc62ca6) - Bug 1228984 - [css-grid] Add more auto-placement tests. (6c2bfceefd) - Bug 1215182 - [css-grid] Make our "Implicit Named Areas" detection match the spec. r=dholbert (a31e1afe0f) - Bug 1215182 - Reftests. (22e235d090) - Bug 957911 - Work around the lack of support for semi-colon comments in python/configobj. r=gps (3f65ecdb57) - Bug 1194121 - Skip UpdateCommands() from initializing collapse to avoid sync IPC during app startup. r=jst (f84caa230a) - Bug 1170642 - Silence nsDocumentViewer::GetInImage warnings. r=ehsan (1e652f7f35) - No bug, use attached widget listener mode on iOS, NPOTB (394650156a) - Bug 1191609 - Always stroke CSS border sides separately from corner fills. r=mstange (c84f179c91) - Bug 1224761 - Fix forceRepeatToCoverTiles optimization to not trigger when all stops at left edge of tile. r=roc (8a95296996) - Bug 1155766 - Fix a bad assertion r=jfkthame (db12ebcfab) - Bug 1163583 - Update SetPara with recent changes to ICU algorithm. r=smontagu (29250e8018) - Bug 1157727 - Part 0: Preliminary cleanup, remove a bunch of #ifdef'd dead code from nsBidi.cpp. r=smontagu (b6b1bafd0c) - Bug 1157727 - Part 1: Add paired bracket type property to our character data (patch originally by :tedders1, updated by :jfkthame). r=jfkthame (dd3b21469a) - Bug 1161932 - Fix coverity warning in nsBidi.cpp. r=smontagu (8c5e758aad) - Bug 1217833 - Fix container width in exception for line frames in nsBidiPresUtils::ReorderFrames. r=jfkthame (b59949333a) - Bug 1217833 followup - Mark one test as fuzzy(43,2) on a CLOSED TREE (though fuzzy amounts needed vary by platform). (241f74b354) - Bug 1217833 followup - Add margin to avoid fuzz on reftest. (e885281263) - Bug 1157727 - Reftests for bidi bracket pairing, based on UAX #9 examples. r=smontagu (a6865a934c) - Bug 1157727 - Part 2: Update bidi algorithm for bracket matching (patch originally by :tedders1, updated by :jfkthame). r=jfkthame (1bf541ba42) - Bug 1169088 - Remove unused nsBidiPresUtils methods. r=dbaron (27a86233bc) - Bug 817406 part 1 - Let ApplyStyleFixups propogate 'direction' to the viewport. r=bz,heycam (9370d38caf) - Bug 1210877 - Make nsBidiPresUtils::RepositionFrame work also for box-decoration-break:clone. r=roc (ec5d29a8a1) - Bug 1162813: filter paragraph separators before passing text to SetPara, r=jfkthame (4b0fa94ac8) - Bug 1146112 - Mark ruby pseudo frames as line participant in frame constructor. r=roc (ae06cf850f) - Bug 1228033. When not painting to a window (and hence not retained) only have one AGR, the root AGR. r=mattwoodrow (f640ec9a8c) - Bug 927228 - Allow ImageLayerization for images using 'contain' and 'cover'. r=mstange (23863c225a) - Bug 1230696 - Don't report perspective values that round to 0 app units as not having perspective. r=roc (9f70c1d9d8) - Bug 1230075 - Allow perspective items in hittest() for preserve-3d cases. r=mattwoodrow (75d585b042) - Bug 1141636 - "Dubious loop test in nsSVGElement::GetAnimatedLengthListValues". r=cam f=longsonr (339c880389) (3850bfcb24) * Notice: the changelog above may not always applicable to XULRunner code which K-Meleon uses. A goanna3 source tree that has kmeleon adaption patch applied is available here: https://github.com/roytam1/palemoon27/tree/kmeleon762 points
-
Thanks again for checking and confirming! Thus, according to your observation, Malwarebytes v1.75.0.1300 is receiving definition updates again. Unbelievable! I will have to try this out at the next opportunity. Maybe, someone else here in the forum is using this version and can confirm this. I had a look at the version history of ZA and searched for announcements. The support of the Internet Protocol 6 (IPv6) seems to have been added only in the version 7.2 points
-
1. Go to "about:config" 2. Locate "plugins.always_show_indicator" 3. Toggle its value (from false -> true) From then on, once you visit a site requiring Flash (or other NPAPI plugin), you'll always get the plugin icon at the left of the URL bar; below, a NM28 screengrab when visiting: https://www.ultrasounds.com/US.html1 point
-
What exactly has changed? I've made this thread back in 2022 to point out much larger spacing between user's profile data and the content of the forum post. This was reduced at some point, so I guess someone on the forum side did look at it. But at present day, after the relatively recent forum update (the one that apparently sent some people into panic mode for the forum not being available for few days), an inconsistency appeared in boldness of fonts between updated Firefox and updated Chromium browsers on the pages with thread lists. See the two images in few posts above (still relevant at the time of writing this post). Both pictures are from Edge, but the text would still appear like in the first picture in Firefox because there's not much (if any) difference between CSS font-weight values of 400 (before forum update) and 500 (after forum update) on that browser, the value of 500 being used since the update that makes the text noticeably bolder in Chromium.1 point
-
Somehow I got to try PassIFox (it's in the Classic Add-ons Archive) just now in 2023. It's one of the few available extensions for integration with KeePass for filling user name/password forms. I've been using KeeFox for the long time, it's much more complex than PassIFox, but struggles with the basics eg. when you have multiple accounts for one site and want to choose specific login, at least the recent versions and it has heavy ties with the browser's UI specifics. Though KeeFox also has more sophisticated URL matching options for instance. I looked at KeeFox's history a bit and one commit dumping support for pre-Australis UI is so huge that it gives me a headache and not having a talent for coding doesn't help either. I figured I haven't been using the extras in KeeFox, like creating new entries and auto-submit. PassIFox should work with both pre-Australis and Australis UI, though I only tried it on Pale Moon. UI is minimal, no option dialogs, no toolbar buttons, just one or two extra right-click context menu entries when right-clicking user/passwords fields, rest of the options are in the accompanying KeePassHttp plugin for KeePass. I think I'll keep PassIFox and use it instead of KeeFox. The latter is half-broken on browsers without Australis UI and I prefer to avoid Australis, because then I need another extension to put things how they were and even then few things still aren't exactly how I'd like them. Maybe if I wanted to mess with CSS, but meh... I lived with Australis-based Firefox when I felt Pale Moon was too far behind with web compatibility, but things are better today. Although there's one thing I do miss about Australis, you have the icon indicating Flash Player being active in the URL bar. I see nothing in the Pale Moon UI indicating the Flash Player was activated.1 point
-
I don't think that's normal. Though I've seen quite some oddities myself on that OS and can't say I miss it, though I appreciate some refinements like the streamlined file permissions dialog and native taskbar(s) for secondary monitors.1 point
-
The only thing I'm aware of with Serpent is having to use: media.mediasource.mp4.enabled set to false otherwise the sound is distorted in a way that could be described as slow. In any case, setting this to false fixed the sound problem for me. This is a good description of the problem: https://askubuntu.com/questions/1200048/firefox-in-xubuntu-is-playing-mp2t-ts-webm-video-files-with-a-deep-slow (I don't use Linux) Ben.1 point
-
1 point
-
Did you actually read the US gov. labs statement, where they caught Kaspersky injecting malicious code into browsers? Well, the member Vistapocalypse pushes the old version, which is affected! I'm not sure why some members choose to ignore it! I took a leave from this site, I came back, I see the same user pushes the same old Kaspersky, at the same time he declares he never used Kaspersky himself, and doesn't have XP! I find his actions suspicious, to say the least! You?1 point
-
For all owners of a computer with a processor, that does not have more than the SSE instruction set, the air is getting thinner. The number of antimalware programmes that offer real-time protection has shrunk dramatically in recent years. The End Of Life (EOL) of Avast Antivirus 2015 was to be expected in any case. Like all AV providers, old versions are no longer supported after a certain point, and thus no further virus definitions are delivered. As a first measure, I recommend to save the last offline definition updater, when automatic definition updates will stop, to use this version as long as wanted and to have the possibility of a later reinstallation. Here is the link of the definition updater for Avast Antivirus 2015: https://install.avcdn.net/ivps9x/vpsupd.exe And for all those who, like me, have withdrawn their trust in Kaspersky and still need an antimalware programme with a background guard for their old computer after September 2023, there will be another solution beyond Kaspersky. I will write about it soon.1 point
-
Musk now claims Twitter login requirement's "just temporary". Someone trusts him? https://mashable.com/article/elon-musk-twitter-login-requirement-temporary1 point
-
The native Google translate is dropped for anything below v.103, so try this plugin by a well known German company, as a good solution for your troubles. https://www.deepl.com/en/chrome-extension1 point
-
@verta. internal (auto) translate is broken by google for older browser versions. start reading here please... https://msfn.org/board/topic/184624-arcticfoxienotheretoplaygames-360chrome-v1352036-rebuild-1/?do=findComment&comment=12466271 point
-
Thanks for this nice statement! And thanks for your detailed report! I asked you if you'd use the IPv6 protocol because old firewalls like Sygate or old versions of ZoneAlarm might lack of this feature. But the IPv4 protocol is no problem for them, of course. Are you still receiving most recent definition updates dated of July 2023? As far as I know, Malwarebytes stopped rolling out those updates for all versions below 3. Please be so kind and check again the date and version of your last definition updates! I tried the version 1.75.0.1300 months ago, and it didn't work for me.1 point
-
I think typing in a CMD window the command libase chrome.dll is something everyone can do. No need to upload anything! All is described here. Easy and comprehensible. The phrase "spoon feeding" I learnt from @VistaLover, and he isn't a fan of it, either.1 point
-
That is rather splitting hairs. You start the tool with the default ini file and it generates the address 0x62a00000 for chrome.dll which is logged by libase in its ini file. Seen in this way, the tool has "chosen" it itself. No interaction by the user. But, your further investigation is not uninteresting. I did not examine the calculation of libase's generated base address more deeply. I would do that only if something went wrong.1 point
-
Just to clarify it! These freezes I had did not come regularly, and completely unexpectedly. I will continue to monitor this at the address 0x62a00000 chosen by libase for chrome.dll. When time is available, I will try your address 0x10010000 by using Rebase.1 point
-
Yeah! I totally forgot. It is generated automatically by libase. My fault! If another address is wanted, one has to use Rebase from Microsoft. @Anbima! So, any deleting in the file libase.ini is not needed and does not do anything, either. I used simply libase without any additional settings which presumably can't be made by libase. It is just an automatic tool and does everything by itself.1 point
-
JUST IN: Holland reopening all sectors of society. "Living even longer with many restrictive measures would damage our health and society," Dutch health minister says.1 point
-
Something's definitely wrong with prices in California. I'd say the inflation is bad all over the world too, but California is always overpriced and overregulated . And this manufactured crisis is not over yet .1 point
-
Well , we have an oceanic climate here , very soft winters , if you could even call it a winter . It's about +7(C) during these days. I live in an 18th century house with a wooden oven . I barely use it because I cook on the electric one . But this wooden oven can be used for heating and even forging . I don't have gas pipelines in my house at all. In 2021, the town became part of the transnational UNESCO World Heritage Site because of its famous baths and its architectural testimony . Is it good ? One one hand : yes . On the other : the bloody tourists , lots of them . Esp. the russian ones, the most annoying and very loud. So I went to our nearest repair shop and guess what ? They told me it's pretty normal for the second batch of this hot chip to run this way . I guess you're lucky that you have the first revision chip (this is my guess though). The card works absolutely fine , I had to increase the fan speed though . Now it's about 88 degrees during heavy load. Not bad , considering the fact of only 50 Euro paid. During casual gaming it's about 75-76 (C). Overall , I don't like . I didn't notice any huge improvements over my GTX 980 SSC. I don't need 12GB of VRAM . In most of my games only 4 used at max. I'll search for the black Titan , like you told me , it should be much better . Thanks again .1 point
-
Well , thank you . The problem is , he refused to ship them to me . So I bought Titan X and can't use it . It's a hellish oven way over 95 degrees (celsius). So I went to read and found this . Seems like this card has manufacturing defects. It can't be just so many people reported this out of the blue. No wonder I got it so cheap. I mean , it works , but it's so hot and loud !!! MX4 didn't help. https://www.nvidia.com/en-us/geforce/forums/geforce-graphics-cards/5/197392/just-got-the-titan-x-runs-extremely-hot/1 point
-
At this state of things we need to cover ourselves with a white sheet and crawl to the nearest cemetery because the gaming days are over , unless you have a 10 grand of Euro freely floating around. In 2014 I bought a TOP PC with GTX980 SSC and 16Gb of RAM for *only* 1100 Euro.1 point
-
Certainly ! You mean we should see a German made OS there ? Or a German made CPU , maybe ? I remember there were Thomson made CPUs out there in the wild (1980-1990s) . Do not remember German-made though.1 point
-
1 point
-
Thank you for the swift reply ! That's what I was really afraid of . 8 is too low and FXAA/MSAA makes my games blurry . I need CSAA , at 16 or 32xx. And I was thinking it's something wrong with my card at first ! Now I see the whole maxwell gen. and up are wrong.1 point
-
Hi and sorry for the off-top. I was offered this 8 years old card for dirt cheap. Is it woth it ? My current is GTX980 super OC . [SSC] . I'm not satisfied with it's performance . Also , with the missing AA options . Could you please look at your NVCPL and tell me what is the max available AA settings ? Thank you very much .1 point
-
1 point
-
Me angry ? Gosh no ! I'm a very calm person. I'm just sitting here and patiently waiting for (at least) 40 years for a German OS to arrive ... What , no ? Still no ?1 point
-
I remember when all those talks about porting DX10 to XP started . Fifteen years ago. We shall be in our late 50s or 60s in another 15 years . So , yeah , why not , let's wait another 15 years for nothing . Please remind me in another 15 years .1 point
-
And how do you know this ? Was there a statement from MSFN employees ? We have to assume the worse case scenario , until proven otherwise , agree ? "conspiracy theory" is a term invented by the FBI to mock people who tell the truth . I'm guessing in 2021 , when 99% of "conspiracy theories" became true you could just drop it , especially among us , privacy seekers , agree ? Chips under human's skin is no longer a "conspiracy theory" . Depopulation and all of the globalists' agendas are also no longer conspiracy theories. REDS taking over America , etc . MSFN with their keylogger are just innocent lambs ....1 point
-
1 - Yesterday it was 452 , YES , 452 !!! Then he edited the post . Why ? Don't want to make any assumptions , but it looks like someone's just seeking for attention . But for quite some time MSFN logs our activity with a new keylogger (yes!) , so it's all in their logs forever. 2 - Doesn't mean they work on XP . For example, DOA 5 wants DX9.0C but still won't start on XP.1 point
-
Now I understand why we have to deal with an absolute crap software in the last 15 years.1 point