Our great sponsors
-
WebKit
Home of the WebKit project, the browser engine used by Safari, Mail, App Store and many other applications on macOS, iOS and Linux.
-
password-manager-resources
A place for creators and users of password managers to collaborate on resources to make password management better.
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
Most platform vendors have this in some form or the other. WebKit has far more here, for example: https://github.com/WebKit/WebKit/blob/main/Source/WebCore/pa.... These are cool and all for when you want software to keep working, but if you're the person writing these, the one thing you should absolutely make sure to do is reach out to the authors of the software you're working around to see if they are willing to fix their code. Most of the time they are! But I invariable see code go into the OS/browser/whatever and engineers bemoaning how they have to work super hard on backcompat, and I'm like…"ok, but when did you send us a bug?"
Apple has a list of websites with quirks that don’t support its “generate strong passwords” feature even though there is HTML spec where you can specify the types of passwords you support.
https://github.com/apple/password-manager-resources
Firefox will also rewrite YouTube embeds: https://searchfox.org/mozilla-central/rev/c6d17806faef8708b6....
Firefox also ships a "system" add-on (https://github.com/mozilla-extensions/webcompat-addon) that has interventions and user-agent overrides for many websites. See for yourself in Firefox on about:compat.
It looks like there was even some discussion of making this behaviour part of the standard, since it's implemented by all of the major browsers.
https://github.com/whatwg/html/issues/2390