The Interop initiative is so cool. Seeing that kind of collaboration across competitors is a delight. And the effect on the #WebPlatform is terrific.

A nice touch: the coordination is so good that all actors publish their take on it at the same time (5pm UTC).

Alphabetically:
- Apple https://webkit.org/blog/14955/the-web-just-gets-better-with-interop/
- Bocoup https://bocoup.com/blog/interop-2024
- Google https://web.dev/blog/interop-2024
- Igalia https://www.igalia.com/2024/interop-2024-launches.html
- Microsoft https://blogs.windows.com/msedgedev/2024/02/01/microsoft-edge-and-interop-2024/
- Mozilla https://hacks.mozilla.org/2024/02/announcing-interop-2024/

#WebStandards

The web just gets better with Interop 2024

The web is amazing.

WebKit

@keybits @jaffathecake In a world without constraints, I would also love to see that API cross-browser (including https://github.com/WICG/navigation-api/issues/225).

But prioritisation is always a difficult exercise, especially across different orgs. As I wasn't involved in the selection process, I don't know why it isn't included: Does this API match the criteria to be selected? Did a vendor not want it in this batch? What other topic would have been dropped to make room for this one?

Fingers crossed for 2025!

Event property to access the element who triggered a navigation · Issue #225 · WICG/navigation-api

I think this new API could be very interesting for a library like Hotwire Turbo. The Turbo Frame concept would need to know if the navigation was triggered by an element or not and if that element ...

GitHub
@anthony @keybits I believe a vendor vetoed it.
@anthony This is really cool, especially after just a few days after some people attacked me saying Google Browser Is Taking Over The Internet.
It is good to see how they really try to converge towards a common standard.