Learn how browsers are working together to make it easier to build for the web

Making a web application work in the same way across browsers can be hard. Learn why these interoperability problems happen, how browsers are working together to prioritize the issues most problematic for developers, and find resources to better understand the gaps in support where they still exist.
Resources:
Bridging the gap: making it easier to build for the web → goo.gle/3vcOLsA
Interop 2022: browsers working together to improve the web for developers → goo.gle/3rjw0Tf
Speaker: Rachel Andrew
Watch more:
All Google I/O 2022 Sessions → goo.gle/IO22_AllSessions
Web at I/O 2022 playlist → goo.gle/IO22_Web
All Google I/O 2022 technical sessions → goo.gle/IO22_Sessions
Subscribe to Google Chrome Developers → goo.gle/ChromeDevs
#GoogleIO

[@jaredwhite88]

All of the new web specs & compat videos this year have been fantastic! I'm incredibly excited to see all the browser vendors and teams working together on such a high level and with such a clear vision. The pace of improvement has been breathtaking and will improve the lives of all web developers no matter which platform they happen to use. The promise of open source and open protocols becoming fully realized…you just love to see it.

[@Joshua-dc4un]

It makes sense for there to be a gap in implementation for the gap property

[@brentmcd12]

this definitely is going to take a while . but at least it's being worked on .

[@saintpyo]

The Interop dashboard seems like a great resource! It's nice to be able to track progress and see what is being actively worked on to improve interoperability. I hope that all those clams of working together are true and I will be regularily checking the dashboard.

[@dogoku]

Great video and thank you for your hard work.

[@UliTroyo]

I was surprised that so many features seemed to be landing simultaneously; I don't know how I missed why it was happening. Great news for the web!

[@Michaelnjuguna1]

Implementation of custom scroll bars in firefox is bad

[@zizifn9142]

wow cross team communication is hard, but you are doing cross communication between different company team. Thanks.

[@aquastias]

Hopefully this will push Apple engineers in the good direction. Safari got a reputation nowadays as being the new IE from the old days. For us, front-end devs, it's really a PITA to make CSS work in that browser.

[@ria8850]

Safari actually have the highest score in the interop 2022 dashboard right now!~

[@SebastianZartner]

@@ria8850 The reason why it has the highest score right now is because it already has new features like all the color related things. Though if you have a look at the 2021 focus areas and "web compat" as general point, you can see that it still lacks behind a bit. And historically, Apple wasn't very cooperative or communicative regarding what they are working on. Though luckily, things have changed now and it's great to see that all browser vendors (finally) are working together to get new features shipped more synchronously and fix existing incompatibilities.

[@kr30000]

Really excited for the future of the web!

[@ria8850]

3:28 subtitles should be: They could then go look, check can I use *or MDN*

[@rnater7145]

lands-in-firefox::after { display: grid; gap: 2yrs }