browser-compat-data

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.