We believe that working with other browser vendors in the context of the WECG is the best path toward a healthy ecosystem that balances the needs of its users and developers. For Mozilla, this is a long term bet on a standards-driven future for WebExtensions.
- This is broadly a very good read for the benefits of Manifest v3. The discussion about Event Pages, ServiceWorker and backgrounding is an interesting read too. I love Service Workers and Web Workers but I still feel there should be another area to interact with DOM API's if there isn't a commitment from the Web-side of the spec world to bring more compute into workers.
- Further reading: https://extensionworkshop.com/documentation/develop/manifest-v3-migration-guide/
- Joyful Little Worlds - this was also pet hobby of mine when I was in University
- Read [public] Attribution Reporting: Strategies and tips for summary reports - Google Docs
- Read Building Interoperable Web Components That Work | CSS-Tricks - CSS-Tricks
- Read / Watched - SCQA - Executive Communication w/ Harrison Metal | Heavybit
- I loved the narrative presented here, but also that the entire presentation was written up and also the video is a super interesting aspect ratio that only makes sense in a page. great!
- Read How to pick the least wrong colors
I lead the Chrome Developer Relations team at Google.
We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.
Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on web.dev, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.
