The article <a href="https://webkit.org/blog/14955/the-web-just-gets-better-with-interop/" author="Jen Simmons" source="Webkit Blog">The web just gets better with Interop 2024</a> writes, <bq><img src="{att_link}interop_2024.jpg" href="{att_link}interop_2024.jpg" align="right" title="Interop 2024" scale="25%">The Interop project aims to improve interoperability by encouraging browser engine teams to look deeper into specific focus areas. Now, for a third year, <a href="https://www.apple.com">Apple</a>, <a href="https://bocoup.com/blog/interop-2024">Bocoup</a>, <a href="https://web.dev/blog/interop-2024">Google</a>, <a href="https://www.igalia.com/2024/interop-2024-launches.html">Igalia</a>, <a href="https://blogs.windows.com/msedgedev/2024/02/01/microsoft-edge-and-interop-2024/">Microsoft</a>, and <a href="https://hacks.mozilla.org/2024/02/announcing-interop-2024/">Mozilla</a> pooled our collective expertise and selected a specific subset of automated tests for 2024. Some of the technologies chosen have been around for a long time. Other areas are brand new. <b>By selecting some of the highest priority features that developers have avoided for years because of their bugs, we can get them to a place where they can finally be relied on.</b></bq> When we complain about features that remain unimplemented in browsers, we also have to acknowledge that there’s only so much you can do with a given team. There are problems that are technically easier to solve than others. When we complain, we’re actually more concerned about the <i>prioritization</i> of issues. We want to be able to influence what gets fixed when, rather than just having to passively hope that the manufacturer eventually gets around to it. That where the <a href="https://wpt.fyi/results/?label=experimental&label=master&aligned">Web Platform Tests</a> come in. The <a href="https://wpt.fyi/interop-2024?stable" author="" source="">Interop 2024</a> project follows on iterations from <a href="https://wpt.fyi/interop-2023">2023</a>, <a href="https://wpt.fyi/interop-2022">2022</a>, and <a href="https://wpt.fyi/interop-2021">2021</a>, when it all started. Last year was a banner year. For CSS <iq>Subgrid, Container Queries, <c>:has()</c>, Motion Path, CSS Math Functions, inert and <c>@property</c> are now supported in every modern browser.</iq> For JavaScript, we got <iq>Improved Web APIs include Offscreen Canvas, Modules in Web Workers, Import Maps, Import Assertions, and JavaScript Modules</iq> across all modern browsers. These are all super-important features. E.g., <i>Import Assertions</i> for JSON import and <i>Modules in Web Workers</i>, which allows modern and modular programming, making it much easier to offload work, as one would with code running directly on modern operating systems. What's on the schedule for 2024? <ul> Although there was a lot of progress made on CSS nesting last year, it's back on the radar this year to finalize the implementations. <c>@property</c> will similarly be more polished, as the percentage support is still quite low in many browsers. It's great to see accessibility improvements for many of these features---like how <c>sub-grids</c> or <c>display: contents</c> affect element order---as this means that we will get sites that are automatically accessible, as long as we build our sites logically. Improvements to <c>IndexedDB</c> will make it easier to write powerful local-first applications (even though something like <a href="https://automerge.org/blog/2023/11/06/automerge-repo/" author="" source="">Automerge</a> might be a better fit for apps offering concurrent or collaborative editing). Browser- and standards-level support for <c>popover</c> with <i>anchors</i> is long overdue, as making usable tooltips and popups is an area fraught with custom code and half-baked solutions. It's nice to see this become an area where you'll no longer need custom JavaScript. <i>Relative Color Syntax</i> continues the excellent trend of allowing us to write CSS without the support of a CSS preprocessor. With relative colors, dark/light theming support, CSS nesting, and CSS variables, I can't think of a reason I would use a CSS preprocessor anymore. I know some people have used them for so much more, but I've not done so, so my needs are already covered, even without this extension that allows conversion between colorspaces. <c>@starting-style</c> will fill a gap in CSS that finally allows sites to indicate how an element will transition from or to <c>display: none</c>. </ul> See the original article for much more detail.