Two ideas for improving MDN’s browser compatibility tables:

GitHub

Browser compatibility: show “No” versions, 2 columns for Node.js · Issue #759 · mdn/mdn

Proposal Thanks for the MDN browser compatibility tables – they are an invaluable feature! Two improvements that I’d find useful: Even if a fea...

Converting to and from Base64 in #JavaScript: > Uint8Array.of(0, 1, 2).toBase64() 'AAEC' > Uint8Array.fromBase64('AAEC') Uint8Array.of(0, 1, 2) Decent JS engine support:

Uint8Array.prototype.toBase64() - JavaScript | MDN

The toBase64() method of Uint8Array instances returns a base64-encoded string based on the data in this Uint8Array object.

“[With] Chrome 154 in October 2026, we will change the default settings of Chrome to enable ‘Always Use Secure Connections’. This means Chrome will ask for the user's permission before the first access to any public site without HTTPS.” I’m ambivalent: Browsers already use HTTPS as much as possible. They should really test if non-technical users understand what the warning says. Otherwise it may scare them away from older sites that would still be useful for them.

Google Online Security Blog

HTTPS by default

One year from now, with the release of Chrome 154 in October 2026, we will change the default settings of Chrome to enable “Always Use Secu...