Journal / Development
Use the new web. Keep the old web working.
The browser is taking on more interface behavior. Shipping it well starts with a fallback.
A broader interface toolkit
Chrome’s Google I/O 2026 web UI overview covers new work across scrolling, anchored interfaces, shapes, and state-preserving DOM changes. It also explicitly marks some features as experimental or proposed. That distinction matters: a conference demo is a useful direction of travel, not proof that a feature works in every visitor’s browser.
Separate shipped from experimental
Choose a real interface problem before adopting a feature. A menu might benefit from better positioning; a dashboard might need scrolling contained within a panel. Test the exact behavior in the browsers your audience uses, then make the enhancement conditional. A visual effect can disappear gracefully. Navigation, form submission, and access to content need to keep working without it.
Our take
The best use of a platform feature often removes code rather than adding spectacle. Maintain one clear baseline, enhance it when support is present, and test input methods as well as viewport sizes. Include keyboard focus, the mobile keyboard, reduced motion, and nested scrolling in the review. New CSS is valuable when it makes the interface easier to understand and the implementation easier to maintain.
Put it into practice.
Pick one existing workaround. Prototype its native replacement, record browser support, and verify the fallback before removing the old code.
Sources & further reading
Editorial analysis by BEMATE. Sources reviewed 6 September 2026.