Google Chrome | July Web Platform Updates Expand Browser Features
The web platform gained another round of useful frontend capabilities during July 2026 as Chrome 151, Firefox 153, and Safari 26.6 reached stable release. The month's changes cover HTML parsing, CSS, animations, media, internationalization, IndexedDB, permissions, and browser fixes, while upcoming beta releases preview even more tools that may influence future interface and template development.
July brings new building blocks for modern web interfaces
One of the most interesting changes for interface work arrives in Firefox 153, which updates how the browser parses content inside the HTML <select> element. Nested elements can now be represented in the DOM instead of limiting the structure to the small set of elements traditionally accepted by select controls.
This does not by itself complete the customizable select experience, but it removes another interoperability obstacle. For web designers, native form controls becoming more flexible could eventually reduce the need for custom replacement components that reproduce dropdown behavior with additional JavaScript and accessibility work.
Chrome and Firefox expand CSS, animation, and web APIs
Chrome 151 adds the ruby-overhang CSS property for controlling how ruby annotations interact with surrounding characters. It also introduces declarative manual slot assignment for Shadow DOM and adds an animation property to AnimationEvent and TransitionEvent, allowing scripts to access the underlying animation object directly from an event.
Firefox 153 adds desktop support for the Picture-in-Picture API and expands Intl.Locale with methods for retrieving information such as calendars, time zones, numbering systems, and week conventions. These locale methods are now Baseline Newly available, making them more practical for interfaces that need to adapt formatting and regional behavior without relying entirely on separate internationalization datasets.
Data and permission workflows also gain new options
Firefox now supports IDBObjectStore.getAllRecords() and IDBIndex.getAllRecords(), providing a simpler way to retrieve complete IndexedDB records without building the same cursor iteration logic manually. Chrome 151 also adds textStream() to Response, Request, and Blob objects for working directly with streams of decoded text.
Another notable Chrome addition is the initial <usermedia> capability element. It provides a declarative, user-initiated control for requesting camera and microphone access, creating a clearer relationship between the user's action and the browser permission prompt. This could become particularly relevant for web apps that rely on recording, conferencing, or other media input workflows.
Upcoming browser betas preview more UI capabilities
The next browser releases are already showing several features worth watching. Chrome 152 beta includes support for additional CSS pseudo-elements, media state pseudo-classes such as :playing, :paused, and :muted, the CSS Color 5 alpha() function, and the global autocorrect HTML attribute.
Safari 27 beta has an especially broad set of CSS and accessibility additions, including ariaNotify, :heading, :host:has(), expanded color-mix(), transform-aware anchor positioning, and other layout and styling improvements. These beta capabilities are useful signals for upcoming web design possibilities, but they should be treated as testing targets rather than production assumptions until their stable browser support is confirmed.
IMPORTANT: Features listed for Chrome 152, Firefox 154, and Safari 27 are currently associated with beta releases. Check stable browser support and compatibility before using them as production requirements in templates or websites.{alertWarning}
Daisuki's Take: What This Means for Web Designers
Monthly browser updates can look highly technical, but many of these smaller changes gradually determine what designers can build with native HTML and CSS instead of custom replacements. The progress toward customizable select elements is a good example: improvements at the parsing level can eventually translate into much more flexible form design.
For template creators, the useful habit is to separate interesting new capabilities from features that are ready to become project requirements. Stable releases can expand the toolkit, while beta releases are better used to understand what may soon become practical and to identify layouts or components that deserve early testing.
We see these monthly platform updates as a preview of where native web design is heading. As browsers converge on more CSS, HTML, accessibility, and interaction features, designers can progressively rely on the platform itself for experiences that previously required heavier custom code.
Sources and Recommended Links
- New to the web platform in July | web.dev Official Site
