Leaderboard

I think we have to take Shane's word for it that the patch has been applied to Supermium 132. As I said earlier, it's an ESR version, which surely should be capable of having the patch applied to it, as it should be fully supported until the next ESR version is released. I'm not sure how we can test whether the patch has been applied successfully or not.

they did this because they want jemalloc to be integrated into C runtime, which is un-recommended by MS later.

Then it's a good idea to use the patched ungoogled for Server 2008 R2. No one knows and no one can guarantee how good and when the old 132 Supermium will (ever?) be patched for that serious vulnerability. https://github.com/e3kskoy7wqk/Chromium-for-windows-7/releases/tag/ungoogled-chromium_138.0.7204.96 Edit/ They say it's been patched in R5. But in the article they say the patch is for 138+! Contradictory. https://github.com/win32ss/supermium/releases/tag/v132-r5

Normally the same as in the PCIe HD graphics card, e.g. AMD HD7450: Audio output from Intel CPU is over HDMI, DP or DVI (DVI only if in bios is function Audio over DVI and you need DVI > DP or DVI > HDMI cable:

Okay. Your suggestion just worked for me as well as FindNextFileA works too when I got mypal68 to work on Windows XP SP1.

Version 138 is required for the fix; the bug goes back earlier though: Good catch. Google is being tight-lipped on exactly when this vulnerability crept in. I doubt it goes all the way back to 2008, though. Today's V8 looks nothing like the original. I believe (and should have said) versions prior to the V8 optimizer are not vulnerable. I suspect 360EE (and Kafan MiniBrowser) aren't vulnerable because the option to turn off the optimizer isn't there (presumably because there's nothing to turn off), but I can't be sure with the limited info we have.

Spring

Iguana

Reading. (town in Berkshire)

Knickerbocker Glory

FYI, my toggle buttons can easily be modified to switch other Boolean preferences. I explained it in the corresponding posts. TBH, there is nothing to be changed in the button's code. I think you rather mean changing the selected preferences which you want to control. This is to be done in the main user interface window of Pref Toggler via the button "Edit List". That's good to hear. Thanks for your feedback!

Did you also try different user agents on this website?

@dmiranda, @Ascii2 Do you still use custom buttons at all? This was actually my initial question. What do you think about custom buttons in general? And have you ever tried the Pref Toggler custom button or my modded version I recently presented here?

You will only know whether these custom buttons are compatible with @roytam1's browsers or not when trying to install them and checking their functionality. Most of these custom buttons are very old. Unfortunately, many of them don't work in Firefox 52 based browsers any longer. They would have to be fixed if possible at all. I personally use only those which are fully functional. My self-created custom buttons have been developed for UXP based browsers and are compatible with @roytam1's browsers and most probably with Pale Moon, too. I even managed some of them to also work in Mypal 68. Have a look here: https://msfn.org/board/topic/183657-mypal-68-in-windows-xp-custom-buttons-and-extensions/?do=findComment&comment=1229639 The more universal the JavaScript coding of these custom buttons, the more compatible. And you have to target only functions which are supported in all browsers. That's why only a few of the old custom buttons can be used in Mypal 68.