Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 01/21/2019 in all areas

  1. 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)
    4 points
  2. I get their point; but the obvious problem is, some of us are already using some WebExtension add-ons in Basilisk, so this breaks compatibility with our browser set-ups. IMO it would be better to leave WebExtensions in the code & just not do any further development on them (except for security fixes). Editorial: I wonder if the PM team is unclear on the problem with WebExtensions. As I see it, the problem isn't that they exist; the problem is that Mozilla decided to force everyone to rewrite their add-ons to use them, in order to install on newer FF versions; thus disabling any legacy add-ons that weren't actively being maintained. This is the main reason I switched to Basilisk in the first place - I didn't want to have to find replacements for all my legacy add-ons - but now the PM team is about to make the exact same mistake, in the opposite direction! Maybe there are also a couple of unstated reasons for the PM team to remove WebExtensions from Basilisk: To remove any incentive to move from PM to Basilisk in order to use newer WebExtension add-ons To further incentivize add-on developers to maintain legacy versions of their add-ons I may have to start using your XP builds even on Win 7, just to keep compatibility with my existing set of add-ons.
    3 points
  3. Personally, I'm not at all content with the decisions made by the Moonchild+Tobin duo... In New Moon 28, I am, of course, confined to only using "legacy" extensions, many of them I inherited from my FxESR 52 usage era; they (continue) to work at this time of writing but the harsh truth is when they start to break (and they will, sooner rather than later ), the chance they receive proper bug fixes, especially those that started life in AMO and haven't been forked to APMO (GitHub?), is minute/none... Recent "troublefests" in NM28 for me include Print Edit 18.4 (a rather convoluted, hack-ish, method to regain basic functionality is to be found in the Pale Moon forums, since the original developer shows no interest at all in fixing his XUL version: all development efforts are focused on its WE counterpart) and Stylem 2.2.4, which is currently bugged and unable to follow the progress made in the UserStyles field; more specifically, it is unable to correctly install configurable userscripts from "UserStyles.org" and has 0 support for the new "trend" that is the "user.css" format (to which many style authors have already changed ...). Even Moonchild himself acknowledges that there is a dim future regarding author support for XUL extensions (intended for consumption by PM/Basilisk users): https://forum.palemoon.org/viewtopic.php?f=46&t=21214 As @Mathwiz has already pointed out, in Serpent 52.9.0 I had found an elegant way to keep on using the greater part of the WEs I was using in FxESR 52; some of these WEs have progressed to versions incompatible with FxESR 52 and/or UXP, so am again forced to using slightly older versions (with no hope of receiving further updates), some others continue to be routinely updated to fix newly introduced bugs; plus, there's always a chance I can find on AMO a new (to me) WE (that I wasn't necessarily using in FxESR 52); in any case, retaining that (rudimentary, at times) WE support in Basilisk/Serpent was always welcome by me,,, For example, I can install and use Stylus 1.4.23 (WE-only) in Serpent 52.9.0, alongside Stylem 2.2.4, to properly install configurable userstyles and "user.css" type styles from GitHub (and elsewhere). And while Moonchild claims: in every day practice that statement is far from being a Holly Truth ; there exist (recent) extensions that only started life in the WE format; as a non-coder, it is impossible for me to "translate" them to the superior XUL format and satisfy Moonchild's expectations... I have quite a few WEs installed in Serpent 52.9.0, these include Google search link fix 1.6.7 ImTranslator: 14.15 (last version properly working) Markdown Viewer Webext 1.4.0 Native MPEG-Dash + HLS Playback 1.1.0 (only available as WE) Play/Pause 2.0.3 uBlock Origin 1.17.7.102 View Page Archive & Cache 1.5.3 Violentmonkey 2.10.1 (only available as WE) Adaptive Bitrate Manifest Viewer 0.9.0 (only available as WE) Browsec VPN - Free and Unlimited VPN 3.16.16 (only available as WE) SaveFrom.net helper 8.1 (only available as WE) Stylus 1.4.23 (only available as WE) ... so I'll be quite frustrated when Basilisk (Serpent) 52 In any case, I might keep a copy of the last WE-compatible version of Serpent 52.9.0, use my copy of Serpent 55.0.0 (which, incidentally, has better WE support) or some other thing... BTW, reddit, ghacks and the like are mostly infested by Mozilla fanbois, who never lose breath badmouthing all Firefox forks (including Pale Moon, Basilisk, Waterfox), so I never place credence to all the FUD they're spreading there... Yes, I am to an extent concerned with browser security, but usability is of primary importance to me... Being on 32-bit Vista, this obviously holds little promise for me... Unless you're implying the Waterfox Team efforts would, somehow, find their way into your forked UXP copy (hence Serpent 52.9.0)...
    2 points
  4. Waterfox team may try to keep them coexist as long as possible
    2 points
  5. don't know if I will follow or not
    2 points
  6. ... This is because Pale Moon 28 (New Moon 28) has a native Site-Specific-User-Agent-Override (SSUAO) for youtube.com that forces it to display in the older ("Classic") web style, which lacks, among other things, the "Watch later" button (placed after "Share" button in the new "Material" web style). general.useragent.override.youtube.com;Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0 PaleMoon/28.3.0a1 If you want to force the new "Material" design for youtube (and thus make the "Watch later" button available to you in NM28), you should modify the SSUAO to spoof a recent Mozilla Firefox version: general.useragent.override.youtube.com;Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Firefox/60.0 Be warned that the Material youtube design works better in more recent hardware (namely GPU/CPU)...
    2 points
  7. 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)
    2 points
  8. You should be able to hide it in Windows/Microsoft Update so it doesn't install again. I assume you've got automatic updating switched on. I would recommend that you switch it off, and configure it just to prompt you when updates are available, not actually install them! IMO it's important to keep control now of exactly what is updated on your machine.
    2 points
  9. New regular/weekly KM-Goanna release: https://o.rths.cf/kmeleon/KM76.1-Goanna-20190119.7z Changelog: Out-of-tree changes: * update Goanna3 to git 35fb6f0f2..de2f91a7b: - 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) * Notice: the changelog above may not always applicable to XULRunner code which K-Meleon uses.
    2 points
  10. NOTE: I originally posted this in the 2000 forum, but it would also be useful duplicated here since XP has such a large user base. As we know, most websites have artificial browser requirements for using their website. Firefox can be spoofed easily on Windows 2000 and XP. I don't recommend Chrome for spoofing, because 1) Chrome does not really work well on 2000, and 2) Chrome can only store user agent changes temporarily, while the Developer Console is open. By visiting Citibank's website with Firefox 48 (last working on Windows 2000), it says the browser is out of date and not supported. So, we go into about:config , create a string value called general.useragent.override , and make the value Mozilla/5.0 (Windows NT 5.1; rv:53.0) Gecko/20100101 Firefox/53.0 This tells the browser to report Windows XP, and Firefox 53.0. Again, we know that XP cannot really support Firefox 53. After saving, reopen Firefox and go back to Citibank's website. The outdated browser warning is gone. This proves an artificial browser warning. Also, if you visit a website to check the browser, it reports that it is Firefox 53 on XP, even though we know we are running Firefox 48 on Windows 2000. This trick will also be useful on XP, since Firefox will not be updated past version 51 going forward.
    1 point
  11. Hey, what do you think about making dedicated board for roytam1's Firefox-based browser builds having a dedicated board somewhere in https://msfn.org/board/forum/102-member-contributed-projects/ ? Currently everything is discussed in one topic: Which has already grown into megathread with different bug reports, questions, discussions related to roytam1's browsers... and they're quite many of them. Trying to find relevant info is getting quite hard with the volume :/ Dedicated board will help a) users to easily find his area of interest in the topic dedicated to his build/issue/question/suggestion b) help author to keep track of a separate issues. As the browsers seem to be popular among MSFN users, this is getting needed. Users, please vote in the poll to show if you agree Admins, mods, is this possible to happen? I contacted roytam1 beforehand and he agrees Plus, if the board gets created some redirection link in XP board will be helpful, as the browsers builds aim at XP compatibility, obviously PS turned voters visibility on.
    1 point
  12. @Mathwiz You may do so through ublock origin
    1 point
  13. I was about to suggest you try that! It seems to be a variant of Murphy's Law: Every "upgrade" will include one or more actual downgrades.
    1 point
  14. Thanks for the clarification. Good to know that "appears to be corrupt" might only mean "not supported." Since I, personally, don't use WebRTC, I just disabled it in about:config on my browser. But as I posted, someone who does use WebRTC needs a more convenient way to toggle it on/off.
    1 point
  15. Yeah, Defender now detects some of my tools a as virus. So MS blocked my entire outlook account Well new link to v18.10 on first page.
    1 point
  16. Thanks for showing me how to rescue my Word. I have a feeling that Microsoft doesn't like so many of us using our "free" Office programs! That we all purchased many moons ago!
    1 point
  17. I reinstalled 7.38 a few weeks ago, and today the update nag came back. Back on 7.36 now.
    1 point
  18. AFAIK the only current problem update is KB4461614. Uncheck it and hide it when you see it in the Microsoft Update list.
    1 point
  19. 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
  20. *** This FIX from RT for BNAV Browser Language Packs seems NOT working anymore *** @roytam1 ==> To use SM-2.49 LangPack in Borealis, some changes have to be done in SM LangPack <== Okay, this RT modification WORKS (THANKS!) for (SeaMonkey) SM-2.49 LANGPACK with RT Borealis Browser: https://o.rths.cf/boc-uxp/ I have repeated and 'enhanced' the RT initial message posting, for intended clarity. The SM-2.49 LANGUAGE PACKS are located here: https://www.seamonkey-project.org/releases/#langpacks *** RT Message (Below) *** (Note: Using 7-Zip and Notepad++ free softwares) If you really want to use SM-2.49 LANGPACK in RT Borealis, these changes (SM LANGPACK) have to be done: - Add this in install.rdf (file ; adding 'code' appropriately 'nested' at bottom) <em:targetApplication> <Description> <em:id>{a3210b97-8e8a-4737-9aa0-aa0e607640b9}</em:id> <em:minVersion>0.1.0a1</em:minVersion> <em:maxVersion>*</em:maxVersion> </Description> </em:targetApplication> - Copy (sm langpack) chrome\<langcode>\locale\<langcode>\communicator\console\console.* (2 Files) to (sm langpack) chrome\<langcode>\locale\<langcode>\global\ - Copy datetimebox.dtd (file) from (RT Borealis Browser) omni.ja ; omni.ja = decompress file (7-Zip) to (sm langpack) chrome\<langcode>\locale\<langcode>\global\ (and translate) - Copy communicator\consoleOverlay.dtd (file) from (RT Borealis) omni.ja ; omni.ja = decompress file (7-Zip) to (sm langpack) chrome\<langcode>\locale\<langcode>\communicator\ (and translate) - Modify (sm langpack) chrome\<langcode>\locale\<langcode>\global\findbar.dtd (file), 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 (file), adding (and translate) these: <!ENTITY bookmarkTab.label "Bookmark This Tab"> <!ENTITY bookmarkTab.accesskey "B"> Then at least it won't stop working after applying sm langpack. (Note: RT by "and translate" means "Next" becomes "Siguiente" (Spanish) ; do for all 'label' entries) *** RT Message (Above) *** *** 'about:config' ; Changes for LANGUAGE PACK activation (Below) *** URL Reference: http://addons.palemoon.org/language-packs/ "general.useragent.locale" Which is set to "en-US" by default. Change to say "es-ES" for SPAIN (Spanish Language) "intl.accept_languages" Which is set to "en-US, en" by default. Change to say "es-ES, es" for SPAIN (Spanish Language) *** 'about:config' ; Changes for LANGUAGE PACK activation (Above) *** (Note: Borealis "omni.ja" is a compressed file. Use 7-Zip to decompress and access RT referenced files)
    1 point
  21. Hi all, Just a quick line to say you saved me before Christmas a couple of times and twice this week with that KB4461614 update! It keeps making its way back to my computer but really thankful for your help. Best wishes, Nora
    1 point
  22. 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 langpack
    1 point
  23. New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rths.cf/boc-uxp/mailnews.win32-20190119-d31e5ac-uxp-082c0d218-xpmod.7z Browser-only Suite Win32 (removed due to request) source patch (excluding UXP): (removed due to request) Official repo changes since my last build: - [PLATFORM] Update commit pointer (de85ad0) - Clean up automated build infra mozconfigs (5813a8b) - Move things so they will be better placed (ae836e4) - [MAIL] Eat the space on double-click word selection (792ee0b) - [MAIL] Do NOT Eat the space on double-click word selection (d31e5ac) For UXP changes please see above.
    1 point
  24. 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)
    1 point
  25. Perhaps, but I think there has been as much or more, and definitely more recent, activity as the various topics under Other Member Contributed Projects. Since, I assume, the browsers can be used in OS other than XP, that might help raise awareness and interest. If a section was created there, and IF more activity was created as a result, then the discussion of whether or not to create a section higher up under Member Contributed Projects could be raised again at that time. Just my two cents, of course.
    1 point
  26. No idea about subsections, but what's long since needed are separate topics for separate browsers (NewMoon, Basilisk, rzbrowser, rz-suite, KG, ...) The prob is, I asked him before, but he declined as usual for such user needs, because they are not his own needs. But if more people care now, perhaps there's finally a chance :-)
    1 point
  27. Just download a language pack from here: https://addons.palemoon.org/language-packs/ And set the general.useragent.locale pref in about:config to es-AR (since I'm assuming you want to install a Argentinian Spanish LP.) You also have more detailed instructions there. And whenever NM's version changes to 28.4, you'll need to follow @VistaLover's instructions on what to do in order to have the LP working again (except the Step 1 to download a polish language pack obviously): Alternatively you can wait till there are 28.4 compatible, RC versions of language packs available here: https://github.com/JustOff/pale-moon-localization/releases
    1 point
  28. It did NOT play in Firefox 52.9 ESR Browser either. However, it did PLAY okay in CHROME 49 (ver.) Browser. It is a bit 'odd size' video (640x800), but unclear that it matters. It is not corrupt -- it did play in CHROME .
    1 point
  29. Specifically, WebRTC leaks two bits of info that may compromise your privacy: Device ID hashes for your microphone & camera The IP address on your local network #1 can be used for browser fingerprinting, allowing the likes of Google and Facebook to secretly track your online activities; luckily it's mostly a problem for Chromium-family browsers, not for Firefox-family browsers like Basilisk. The latter browsers randomize the "salt" used in the hash whenever the browser is started, so unless you leave your browser session running for weeks at a time, the ability of anyone to use #1 as a secret tracking cookie is limited. #2 is more problematic though. It can reveal your "real" address behind a VPN, which could be used for censorship, or alert the authorities that you're accessing "banned" material. More commonly, it will reveal one of those non-routeable local IP addresses starting with 10. or 192.168 assigned by your (real or virtual) router. That's less worrisome, but if it doesn't change often, it too can be used in conjunction with your public IP for browser fingerprinting. If you don't need/use WebRTC, the website linked above contains instructions for disabling it and preventing those info leaks. But what if you do use it? One solution might be the WebRTC Control add-on. This adds a toolbar button that simply toggles WebRTC on or off, a la the popular Flash Disable add-on. So you can leave it off for normal browsing, but turn it on before going to a site that requires it. Edit: Should have checked first. Couldn't install WebRTC Control linked above. All three versions download OK but Basilisk reports that they all appear to be corrupt. Must be a bad hash somewhere Try the "classic" version of Disable WebRTC instead. I think a better solution would be an add-on with a white-list, which would enable WebRTC automatically, but only for sites like Discord and Skype. But I haven't yet found a Basilisk-compatible add-on that has such a white-list
    1 point
  30. @JohnnieB, you can find out what updates you've received and the dates they were downloaded to your system by running Windows Security Centre and invoking the "Check for the latest updates from Windows Update" option (menu on left), then selecting the "Review your update history" option in the Windows Update explorer window which will subsequently appear (left side menu again, top option). Cheers!
    1 point
  31. Well, it's that time of the month again, and only a year away from Vista's true EoL (or EoS, as @dencorso has said about XP, though not sure if it applies to Vista as well)... And as usual, I recommend waiting at least a week before any of these, because we never know, if Microsoft won't pull any of these updates and upload it (or even more than one of them) again in a couple days. So, without further ado, let's finally get to what you all have come here for: KB4480968 - Security Monthly Quality Rollup for Windows Server 2008 - 32-bit | 64-bit KB4480957 - Security Only Quality Update for Windows Server 2008 - 32-bit | 64-bit KB4480965 - Cumulative Security Update for Internet Explorer 9 for Windows Server 2008 SP2 - 32-bit | 64-bit KB4481486 - Security and Quality Rollup for .NET Framework 2.0, 3.0, 4.5.2, 4.6/4.6.1 for Windows Server 2008 SP2 - 32-bit and 64-bit update catalog link KB4480062 - Security and Quality Rollup for .NET Framework 2.0, 3.0 for Windows Server 2008 SP2 - 32-bit | 64-bit KB4480059 - Security and Quality Rollup for .NET Framework 4.5.2 for Windows Server 2008 SP2 - 32-bit | 64-bit KB4480055 - Security and Quality Rollup for .NET Framework 4.6/4.6.1 for Windows Server 2008 SP2 - 32-bit | 64-bit KB4481487 - Security Only Update for .NET Framework 2.0, 3.0, 4.5.2, 4.6/4.6.1 for Windows Server 2008 SP2 - 32-bit and 64-bit MS update catalog link KB4480084 - Security Only Update for .NET Framework 2.0, 3.0 for Windows Server 2008 - 32-bit | 64-bit KB4480076 - Security Only Update for .NET Framework 4.5.2 for Windows Server 2008 SP2 - 32-bit | 64-bit KB4480072 - Security Only Update for .NET Framework 4.6/4.6.1 for Windows Server 2008 SP2 - 32-bit | 64-bit Extra/optional update: KB4487354 - Update for Windows Server 2008 SP2 for x84/x64 based Systems - 32-bit | 64-bit I think that's all for this month (for now at least), except 2 updates for Itanium based systems only, but I don't think it's necessary to post them here. I also hope you all will like this new way of posting lists of updates which are available for Vista, and which I will try to use from now on. I also apologize for no direct links to bigger .net rollups but direct downloads of those are sadly unavailable. Added KB4487354, thanks to @mike_shupp for finding it.
    1 point
×
×
  • Create New...