3 ms·

Browsers don't usually break older pages. The only time this happens when you rely on unstandardized features. At least, I have not noticed any page breaking in

by tinco 5y ago

Browsers don't usually break older pages. The only time this happens when you rely on unstandardized features. At least, I have not noticed any page breaking in the past 15 years except for the ones I built using unstandardized API's.

mappu 5y ago
The changing behaviour of browser autocomplete and the new disregard for autocomplete="off" really harmed multiple large CRM / ERP-style sites i worked on, as passwords would get "helpfully" autofilled into completely wrong fields, causing data loss. I actually still don't think there's a proper sanctioned solution to this, it seems to be cat-and-moused by web developers and browser developers every year or two.
deleted 5y ago
[deleted]
Macha 5y ago
The largest browser maker no longer believes so: https://www.theregister.com/2021/08/05/google_chrome_iframe/ https://www.theregister.com/2021/08/05/google_chrome_iframe/ https://mobile.twitter.com/estark37/status/1422694856544059396 https://mobile.twitter.com/estark37/status/14226948565440593...
asddubs 5y ago
-https sites embedding http images -SameSite:none cookies (with bonus breakage that makes it impossible to use accross older and newer browsers simultaneously without user agent sniffing) -the planned chrome alert/prompt changes already mentioned below browsers have been getting a lot more comfortable with the idea of breaking backwards compatibility as of late.
spicybright 5y ago
> except for the ones I built using unstandardized API's. Think you proved my point.