browser-compat-data

This API dates back to 1999 if not earlier.* Lots of APIs back then weren't designed very carefully, and now we're stuck with them. * According to https://github.com/mdn/browser-compat-data/blob/v8.0.6/api/E..., Internet Explorer 5 had it. Unfortunately, I don't know of any way to look up which Netscape versions did.

Links on support: https://github.com/mdn/browser-compat-data/blob/main/manifes... (data integrated into the MDN page I linked) Chromium: https://chromestatus.com/feature/5662315307335680, implemented on Android from M71 and desktop from M89. WebKit: standards position is neutral <https://github.com/WebKit/standards-positions/issues/11>, and https://bugs.webkit.org/show_bug.cgi?id=194593 shows plenty of developer interest but doesn’t look to have been touched by Apple. Firefox: standards position is positive <https://mozilla.github.io/standards-positions/#web-share-tar...>, but https://bugzilla.mozilla.org/show_bug.cgi?id=1476515 has languished.

I honestly never thought to click on those! Thanks very much. Now I'm digging around in https://github.com/mdn/browser-compat-data/blob/main/api/Loc... and trying to find the browser release dates data... Ooh, https://bcd.developer.mozilla.org/bcd/api/v0/current/api.Loc... is even better - it expands those browser dates and it's served with access-control-allow-origin: *

<xmp> and <plaintext> never die! I think/hope/believe that even though these elements fell out of grace of the standard bodies [1] long time ago, implementers simply cannot go against backwards compatibility here and remove them like spec suggest and MDN scaremongers that it "was not implemented in a consistent way" [2], yet last time I checked, the support in major browsers was pretty solid [3]. - [1] yet https://html.spec.whatwg.org/multipage/obsolete.html#xmp tells still acknowledges that "User agents must treat xmp elements in a manner equivalent to pre elements in terms of semantics and for purposes of rendering. (The parser has special behavior for this element though.)" - [2] https://developer.mozilla.org/en-US/docs/Web/HTML/Element/xm... - [3] https://github.com/mdn/browser-compat-data/issues/2168#issue...

> a lot of the data on the site actually comes from MDN Eh... not really. The feature support matrix (as linked on CanIUse) comes from MDN's browser-compat-data repo. Here's the HTML element's source data: https://github.com/mdn/browser-compat-data/blob/main/html/el... This doesn't contain the testing and usage info that CanIUse cites for support, though, just which browser versions included which features. CanIUse also points to their own repo, which contains a lot of data: https://github.com/fyrd/caniuse But I can't find an easy entry point to find where they're getting the numbers for a specific element. The data on there seems to be primarily for features. So the more precise question is, where is CanIUse getting HTML element testing and usage numbers from? Because that seems to be the issue.

( Hi, author of the post here) Thanks for catching this. I’ve updated the post to fix this copy-paste error. CanIUse has no entry for it, as this feature is brand new. The PR add the data (https://github.com/mdn/browser-compat-data/pull/20935) is still pending.

FWIW, OWD writes open source technical content and is not responsible for the design of MDN nor the blog, ads, or login and membership features of the site. That is done by Mozilla. The OWD team writes technical documentation on APIs, HTML, and JS. OWD also works on information architecture and browser compatibility data. They contribute mainly to https://github.com/mdn/content/ and https://github.com/mdn/browser-compat-data/. Mozilla, not OWD, is responsible for Yari, the platform behind MDN Web Docs (https://github.com/mdn/yari). The MDN blog, ads, AI and design, the MDN infrastructure, are fully owned and controlled by Mozilla. I know some folks who work on this content and TBH it’s the folks we’d want working on this content.

Just noting that the browser support matrix is right here: https://web.dev/patterns/advanced-apps/contacts/#:~:text=con... It's an Eleventy widget powered by MDN's browser-compat-data: https://github.com/mdn/browser-compat-data.

i'd guess the mechanisms for ad clicks and search engine refinement are largely separate (with maybe some overlap for sponsored results? does google do that?). the asynchronous ping attribute is new[1]. i'm pretty sure it was the mid-00s when i first noticed that search result links bounced through a redirect via google. (and i'm guessing it was added to reduce confusion when hovering and ameliorate copy/paste issues for search result links, but i don't know for sure) [1] https://github.com/mdn/browser-compat-data/pull/9470 (april 2021)

Here's the corresponding GitHub issue: https://github.com/mdn/browser-compat-data/issues/5476

See also browser-compat-data, the source data for Can I Use? and the Browser Compatibility tables at the bottom of MDN reference pages. I believe VS Code and other tools also rely on it. https://github.com/mdn/browser-compat-data

> - Support for the WebExtensions standard means addons are trickling back into the ecosystem - I'm happy with my AdBlocker and Nightmode extensions The critical functionality required for uBlock Origin and other request-based ad-blockers is blocking using the WebRequest API, which isn't supported in WebExtensions in Safari [0]. [0]: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web... [0]: https://github.com/mdn/browser-compat-data/blob/master/webex...

It seemed quite straightforward to me last time I wanted to update something: there is boilerplate (schema [0]) JSON for feature / subfeature that lists all browsers in current documentation set with `{"version_added": null}` meaning "I don't know if given browser supports this feature" [1]. It's probably fine to introduce feature with completely unknown support just to ease future updates. I'm not sure if introduced feature should be in some advanced standardization process stage or not. For bugs and details in implementations you can use `{versoin_added: true, notes: ["not in conditions described in <a href='...'>some bugreport</a>"]}` [2]. [0] https://github.com/mdn/browser-compat-data/blob/4f34583ab491... [1] https://github.com/mdn/browser-compat-data/blob/master/schem... [2] https://github.com/mdn/browser-compat-data/blob/master/s

I should really write a script to generate this from MDN's browser compatibility data (https://github.com/mdn/browser-compat-data), but many APIs aimed at making browsers more competitive with native apps tend to lag behind or not get implemented at all in Webkit. We only got working IndexedDB as of Safari 10 and Service Workers in Safari 11, both multiple years after support landed in stable Firefox. There's no support for WebXR, Web Push, or WebAuthn. Safari still can't display WebP images, show WebM (VP8/9) movies, or play Opus-formatted sound. Safari doesn't understand the current version of referrer-policy headers. Safari doesn't implement the String.prototype.matchAll() method. There's no support for getDisplayMedia(). Depending on how you count, we've been waiting seven years for getUserMedia() in Safari, and it's still not fully f