@paul heya - about the demo showing AI insights in devtools - it seems kinda (maybe) dangerous to suggest that adding a header to the network request 'fixes' the CORS issue. it really doesn't. am i crazy for worrying its misleading?
For this demo app, this was the correct answer given that "we own" the API.
I felt at the time that it was clear that the header overrides was temporary and shows the solution that you would apply to the backend.
I think where the keynote script maybe fell down was that to make the script work we changed it from a site "we built and own" to "I'm exploring this site"
Error causes shown directly in Console for easier debugging
CSS selector stats in Performance for optimizing page loads
Early Hints headers support in Network tab
Plus the usual array of updates and fixes to help build the future of the web
Lots of helpful improvements for web developers in this release. Check out the article for more details on these updates and how to use them effectively. Happy building!
WebGPU continues to evolve with new capabilities in Chrome 125. The article highlights two notable additions - subgroups for more efficient development of complex scenes, and rendering to a slice of a 3D texture for efficient re-use of texture memory. As WebGPU matures, it unlocks more advanced graphics and computation scenarios on the web. I'm excited to see developers leverage these capabilities to build immersive, high-performance web apps.
Why do CSS and UI capabilities matter for ecommerce? This article explores how implementing modern CSS and UI features like View Transitions, Scroll-driven animations, and the Popover API can enhance ecommerce sites and provide better experiences for customers. As a developer advocate focused on the capabilities of the web, I think this provides great perspective on how we can build more engaging sites.
Exciting update for web developers - the popover API has landed in all modern browser engines. This will allow developers to more easily create contextual overlays on their sites. I'm looking forward to seeing the creative ways devs leverage this new capability to enhance user experiences.
Heads up web developers! The Private Network Access deprecation trial is ending soon. To access private network resources from non-HTTPS sites, you'll need to implement permission prompts to relax mixed content checks. Check out this insightful article for more details on ensuring your sites function properly with these updated security policies. As always, please reach out with any questions!
New on the Web! The JavaScript Intl.Segmenter object is now interoperable, enabling locale-sensitive text segmentation. This allows developers to segment text appropriately for different languages and locales. Exciting new capability for building global web apps! Check it out and let me know what cool things you build with it.
New in Chrome: The CSS align-content property for block layout is now supported, allowing more control over alignment of content along the cross axis in multi-line block layouts. This unlocks new responsive design possibilities. As a Developer Advocate, I'm excited by CSS improvements like this that give developers more tools to build creative web experiences. I encourage you to check out the align-content updates and experiment with them in your projects!
Pete LePage covers what's new for developers in Chrome 124, including two new APIs for using declarative shadow DOM from JavaScript, streams support in Web Sockets, view transition improvements, and more. Exciting updates that push the boundaries of web development!
New in Chrome: Access to MIDI devices now requires user permission
Chrome has updated the Web MIDI API to put user privacy first. MIDI device access now requires explicit opt-in consent through a permission prompt. This allows users to control which sites can interact with MIDI hardware. Kudos to the Chrome team for keeping the web platform open while prioritizing user choice. Exciting to see APIs evolve in thoughtful ways.