browser-compat-data VS caniuse

> 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 the 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.

The key factor for web development to stop new CSS features is cross-platform compatibility. If you want to know the compatibility data of a new feature, you can get it through platforms such as Can I Use , Browser Compat Data and Time to Stable .

Yes, Mozzila’s browser-compat-data (https://github.com/mdn/browser-compat-data) is the authoritative source.

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.

https://developer.mozilla.org Is your best friend, they even have an examples how to use it

Visit any website on https://developer.chrome.com, https://developer.mozilla.org or https://docs.microsoft.com.

W3Schools and MDN Web Docs are two great resources to learn about elements and all about HTML and CSS. Kevin Powell has a great YouTube channel which explains everything you search for. If you want to incline in your HTML and CSS skills pretty quickly, think of your objective, maybe even sketch it out, then search absolutely everything on Google and it will give you the answer. If not, this subreddit is always open. Bon voyage

Safari is the only browser that doesn't support extending HTML element

https://caniuse.com/?search=Custom%20Elements

You forgot to mention (Web)Workers. This is explicit creation, management, and communication with additional threads within JavaScript. What's more, they've been around in JavaScript longer than the V8 engine has even existed!

https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers...

https://caniuse.com/?search=webworkers

Do you happen to know where can I check out the cutoff version for each browser? https://caniuse.com/?search=wasm doesn't have it (or other things like WasmGC for that matter)

(https://caniuse.com/) A handy tool for checking the browser compatibility of HTML, CSS, and JavaScript features. Can I Use provides up-to-date support tables for various web technologies across different browsers.

Caniuse

Can I Use (https://caniuse.com/)

> Is it though?

In my experience it's the buggiest browser out of the big three, and is often missing basic features like e.g.:

https://caniuse.com/?search=opus

Supported in Firefox for *12 years* now, in Chrome for 10, still no support in Safari.

They only "support" Opus audio in their special snowflake '.caf' container, which is super buggy and the last time I checked no open source program could even generate Opus '.caf' files that could be played by Safari on all Apple platforms. I ended up writing a custom converter which takes a standard '.opus' file and remuxes it on-the-fly (I only store '.opus' files on my server) into Safari-compatible '.caf' files, taking special care to massage it so that it avoids all of their demuxer/decoder bugs. You shouldn't have to do this to have cross-browser high quality audio!

Well I'll be! In my mind I had this clear picture of Firefox implementing it.

It correct, it was only Chrome: https://caniuse.com/?search=html%20import