interop VS caniuse

There is popular demand (including from Adobe https://github.com/web-platform-tests/interop/issues/430#iss... ), which is arguably evidence against (2).

Microsoft Edge does support AV1, but weirdly only through a Microsoft Store extension [1], even though Chrome has support built-in. This actually really sucks because in practice hardly any normal consumers would bother to install a strangely named extension, and so web developers have to assume it's largely unsupported in Edge. Safari ties support to a hardware decoder, which I suppose is understandable to avoid accidental battery drain from using a software codec, and means eventually in some year's time support can generally be relied upon when enough new hardware is in use. But that won't happen with Edge as things stand!

I think it's high time the web had a single audio and video codec choice that was widely supported, which is why I've proposed support for AV1 and Opus for the Interop 2024 effort [2] [3].

[1] https://apps.microsoft.com/detail/av1-video-extension/9MVZQV...

[2] https://github.com/web-platform-tests/interop/issues/485

[3] https://github.com/web-platform-tests/interop/issues/484

This is the comment to read:

https://github.com/web-platform-tests/interop/issues/430#iss...

It got me drooling for JPEG XL like I never did for WebP or HEIC.

The Interop group describe this focus area as: "enable testing for font stack capabilities and enable additional expressiveness with vector color fonts. (Font feature detection and palettes)".

I would say that overall InterOp 2022 went well, they completed most of what they planned to do. Of the 15 focus areas, 13 focus areas had an InterOp score of over 80%.

Interop 2023 is under development, the project timeline states that a public announcement will be made this week. 🤞

https://open-web-advocacy.org/walled-gardens-report/#ios-saf...

And

https://open-web-advocacy.org/walled-gardens-report/#evidenc...

Make sure you tap more comments to see the examples.

The number one issue for building native like apps is this https://github.com/web-platform-tests/interop/issues/84

It has been buggy for as long as I can remember and never been fixed.

Not to mention the 10 years of issues with indexeddb or the issues with WebRTC.

Open Web Advocacy has been very clear that they want competition on iOS, not Chrome specifically. The reason being that the absence of competition is currently allowing Apple to deteriorate the web experience on iOS, preventing the web and web apps from competing with native apps. Their objective is to lift these artificial limitations imposed by Apple and free the web.

OWA members have actually been actively reporting WebKit bugs and interacting with the Safari team to help prioritise features and bug fixes on Twitter and elsewhere, showing the goal is to improve the overall web experience on iOS, not let Chrome to become dominant. Here is one of their detailed bug report: https://github.com/web-platform-tests/interop-2022/issues/84.

Container Queries and Subgrid are only available in Safari Technology Preview, not stable, and Firefox has actually been supporting Subgrid for more than 2 years. Because CQ is not supported by either Chrome of Firefox, it will be at least 2 years before we can start actually using it.

It would have been much wiser for Safari to catch up on the dozens of features they don't support that both Chrome and Firefox do, or to focus on bug fixes for the most basic features that's been broken for years. Instead, they chose to ship shiny new ones to try and convince both regulators (from the EU, UK, US, etc) and web developers that they are leading the way in feature adoption. Unfortunately this seems to be working to some extent in the web devs community. Regulators are unlikely to fall for it though.

Here is the 7 years old scrolling bug I'm referring to, which prevents any decent implementation of modals in Safari on iOS: https://github.com/web-platform-tests/interop-2022/issues/84

Here you can see that Safari has 5 times more API failures (representative of both missing features and bugs) than Chrome, and 3 times more than Firefox: https://wpt.fyi/

Can I X, is a question about the readiness/compliance of a certain thing at time = now. Can I use CSS version X was the iconic early meme.

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

For a generalized example, if you wanted to know if the basketball courts were ready for you to “ball it up” in a certain city, it’d be caniball.com

If you want to know if you can use a certain frontend technology, the idea is like: canwefigma?

It’s a glorified feature matrix, and usually a project of a passionate community. I approve, even if some of the memes are a bit dank.

https://caniuse.com/ is a popular tool to check what web features are working across different browsers - "can you use this and assume that it will work for others".

The article uses custom css @properties which are awesome and have 88% browser support [1].

One thing to watch out for is differences in how browsers handle setting the fallback initial-value. Chrome will use initial-value if CSS variable is undefined OR set to an invalid value. Firefox will only use initial-value if the variable is undefined. For most projects, this won't be an issue, but for a recent project, I ended up needing to use javascript to set default values in Firefox to iron out the inconsistency between browser implementations.

[1] https://caniuse.com/?search=%40property

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