Leaderboard

New build of basilisk/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20181124-b37e8f87c-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20181124-b37e8f87c-xpmod.7z diff: https://o.rths.cf/basilisk/UXP-xp-gitdiff-20181110.7z PM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.2.0a1.win32-git-20181124-b37e8f87c-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.2.0a1.win64-git-20181124-b37e8f87c-xpmod.7z Official repo changes since my last build: - Add support to libstagefright for AV1 FourCCs (df59d06fd) - Issue #638 - Part 1: Provide a visual indicator for muting/unmuting tabs (becd71a86) - Issue #638 - Part 2: Add tooltip to mute/unmute buttons (ae48428aa) - Issue #638 - Part 3: Add a keyboard shortcut for toggling the tab mute state (15afe6807) - Issue #638 - Part 4: Add tab sound icon to tab drop-down list (719234847) - Issue #638 - Part 5: Add mute/unmute option to tab context menu (eff89e1c9) - Issue #638 - Part 6: Fix up remaining references - Refactor _tabAttrModified to accept two parameters - Modify consumers of _tabAttrModified to pass details - Add missing _soundPlayingAttrRemovalTimer field - Add missing checks for mute/unmute around the tab browser - Tab sound icon should inherit 'selected' attribute instead of 'visuallyselected' (d56c1ceac) - [PALEMOON] Align the places component with the updated PlacesUtils API (b32323fae) - Issue #638 - Part 7: Remove hover and active states for sound indicator (66cc7d91a) - Issue #638 - Part 8: Add overlay sound icon for pinned tabs - This also moves some styles to tabbrowser.css (a6b250b47) - Issue #638 - Part 9: Add sound icon to all tabs menu (fe4c12e2d) - Issue #638 - Part 10: Rename all tabs sound icon to be consistent with others - alltabs => allTabs (deb4791e2) - Follow-up: Add missing getTabFromAudioEvent method (61b21c808) - Fix undefined isSameDocument (a681891e6) - Hide mute menu item and disable mute hotkey with existing pref (af0164310) - Add support to libstagefright for AV1 FourCCs (part 2) (4d8b7a376) - Add AV1 support to MP4Decoder. (56c26d867) - Replace toolbar PNG bitmaps with SVG vectors. (a5bdec9a6) - Cleanup some comments in our media code. (011ec4885) - Merge pull request #877 from trav90/code-cleanup (181e75728) - Merge pull request #876 from trav90/add-av1-support (f4908ce99) - Merge pull request #873 from JustOff/PR_bm_folders_copy_paste (be53c078d) - Strip Inkscape data from toolbar SVGs and remove obsolete PNGs. (4fd138594) - Merge pull request #874 from FranklinDM/sound_indicator-work (025b91375) - Belated new cycle version bump (9ce2c56e1) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (a6b9afbee) - Add a nullcheck on pipelined HTTP connections' pushback. (2c0a30185) - Update package.json (6a9c2be4e) - Port WebP decoder changes. (238b430ec) - Bug 1462355 - Part 1a. Make imgFrame animation parameters threadsafe. (807acf738) - Bug 1462355 - Part 1b. Update Decoder and SurfacePipe plumbing to use updated imgFrame methods. (622098073) - Bug 1462355 - Part 1c. Make individual image decoders to use updated Decoder/SurfacePipe methods. (3417e581c) - Fix pasta error (b9003c9c5) - Unrefactor mRawVeggies back to mVBuffMeat ;P (5b821064f) - Split out FrameTimeout into its own header file for re-use. (a51993521) - Fix blank pixel color for truncated GIFs (25f4c75d6) - Merge branch 'webp-update' (a3da92549) - Fix debug assertion. (b37e8f87c)

As far as I know, language packs ain't compatible with any version of Basilisk at all. Or rather the PM ones, since there are no language packs specifically for Basilisk.

yea i was just asking , it felt a bit odd , not picking a fight or so

Not sure if it's the right topic to post in but: According to this: https://www.ghacks.net/2018/11/20/running-windows-7-or-server-2008-you-will-need-this-patch/ Beginning in April next year, Microsoft will sign all updates for Server 2008 using SHA-2 instead of SHA-1, also they will release an update about a month earlier that adds SHA-2 compatibility to Server 2008. I just hope that this update will be compatible with Vista as well.

I inadvertently found out that Internet Explorer 9 is again, as of late, able to play back youtube videos, so it appears Google (the owner of youtube) have patched their scripts to cater to IE9; this surely comes as a (nice ) surprise, but the reason behind such a move seems inexplicable to me... Perhaps was to support WS 2008 SP2 (officially supported until Jan 2020), on which IE9 is the only version of the native Microsoft browser to run, but I'm not convinced... For whatever reason, youtube now has been restored to its previous state in IE9, serving standalone MP4 encodes over HTML5 (usually only in 360p quality variant - some videos with more relaxed copyright also come with an additional (HD) 720p variant). As before, there's no way to go full screen: The MP4 decoding relies on system h.264/aac decoders (Windows Media Foundation), which means you need installed both SP2 + Platform Update Supplement for Vista... OT: Notice in the top blue ribbon how Google are eager to push their own (spyware of a) browser, even on a currently unsupported platform (i.e. Vista)...

It is all explained (but not in a convincing fashion) in https://bugs.chromium.org/p/chromium/issues/detail?id=451733#c19 https://bugs.chromium.org/p/chromium/issues/detail?id=451733#c66 as a result of: https://bugs.chromium.org/p/chromium/issues/detail?id=426573 TL;DR : At the time that decision was made, Vista user base was very thin, compared to either the XP or Win7+ one, so for code refactoring/simplification they decided to merge the Vista codepath to the XP one; for Google, it is only numbers that count ; plus, that gave them a perfect opportunity to dump Vista altogether (along with XP) a whole one year prior to Vista SP2 becoming EOL by M$ (and close to 5 years before Vista's Server counterpart, Windows Server 2008 SP2, reaches EOL in Jan 2020 ). Once Google made the first move (dragging along with them all webkit-based browsers), many other software makers soon followed (they had a "nice" justification) in a trend that put Vista, 1.5 years after its official EOL, in the sorry state it is currently in... The only way to properly fix this is to first grab the source for Chromium 41 (-50?) - Chromium, yes, because Google Chrome itself is closed-source - and then revert https://chromium.googlesource.com/chromium/src.git/+/f29562d138f8c2222c6f24bddbd1a665ed036658 Some additional details in https://bugs.chromium.org/p/chromium/issues/detail?id=426573#c10 => https://codereview.chromium.org/755293003/diff/1/ui/base/win/shell.cc#newcode153 This isn't a task for the faint-hearted ... You would need a Win7+, 64-bit, machine with lots of RAM and a powerful multi-core CPU, MS Visual Studio 2013+, lots of time/patience and, of course, you should be well versed in that field (compiling open-source browsers in VS)... Two MSFN members come to mind, @roytam1 and @FranceBB, but I am unsure whether they're interested in compiling Google Chrome 49.0.2623.112 (last officially supported build on Vista) or 50.0.2661.102 (last Vista compatible, but not officially supported) with Aero-Glass enabled in Vista... I, as much as other Vista users, would be all up for this, even if it is realised purely as a challenge only, given that both Chrome 49+50 are quite outdated (in both security and performance aspects) when dealing with the web of 2019... Those two screenshots @VistaPAE posted in OP are not from his own system ... First one is taken from https://bugs.chromium.org/p/chromium/issues/detail?id=451733#c83 That person compiled Chromium 49.0.2579.0 64-bit with the aero-disabling commits reverted... So did this one (Chromium 45.0.2415.0 64-bit) : https://bugs.chromium.org/p/chromium/issues/detail?id=451733#c68 The second screenshot in the OP is taken from https://bugs.chromium.org/p/chromium/issues/detail?id=451733#c67 It emerged that this was actually a hoax/cheat ; the OS used to generate the shot is Win7 SP1 64-bit, disguised as Windows Vista (much like @WinClient5270 's guide found in his signature...) So now you know PS: For the history of it, the last build on Vista SP2 with Aero turned ON was Google Chrome 41.0.2243.0 in the dev channel; I keep a portable copy of it on my system just for fun, it's not used for normal browsing: Next build 41.0.2245.0 had Aero turned OFF in Vista...

Because one can! It's bad netiquette on MSFN to ask such a question... I'd imagine that, at 400, posts you'd know that by now...

That time of the month again, and Microsoft has some Win Server 2008 SP2 updates at the MS Update Catalog site. So far, they've come up with KB4466536 Nov 2018 Security Update for IE 9 KB4467700 Nov 2018 Security Only Quality Update for WS 2008 KB4467706 Nov 2018 Security & Monthly Quality Rollup for WS 2008 KB4467243 Nov 2018 Security & Quality Rollup for .NET Framework (with KB4459933 for NDP 2.0, KB4459945 for NDP 4.5, KB4459942 for NDP 4.6) As usual, I'd suggest waiting a bit before installing things -- Microsoft's been known to change things within a few days (or even hours, on recent occasion). Wait for GreenHillManiac to give them his blessing, that's the safest policy. ----------- And almost as promised, a couple of these did get revised. KB4457700 and KB4467706, the Quality Rollups for Win Server 2008 SP2, were originally dated 9 November. The KB numbers, hashcodes, and sizes don't seem to have changed, but the dates went to 13 November., suggesting some change in the packaging info. Same old spam but a different label on the can, that's my take, but I'm not infallible.