Chrome | 155 Beta Adds CSS Controls for Web Templates
Chrome 155 entered beta on September 16, 2026, with CSS additions for counters, corner styling, text decorations, and container margins. The release gives template developers new patterns to evaluate while keeping browser compatibility and fallback behavior part of the design.
Use the beta to test specific design decisions
The CSS changes touch small but visible parts of a website: list markers, card shapes, underlined text, and spacing around content. They are useful candidates for component tests because each can be examined in an isolated example before it reaches a complete template.
Begin with an existing component that has a clear requirement. A numbered tutorial, a promotional card, or a block of article content makes a better test than a page filled with unrelated effects. Keep the current implementation available so the comparison shows whether the new control actually improves maintainability or appearance.
Counter symbols can be defined where they are needed
The symbols() function defines an anonymous counter style inline, avoiding a separate named @counter-style declaration. It can be used by list-style-type, the list-style shorthand, counter(), and counters(), with several counting systems available.
A designer might evaluate it for a compact sequence of instructions or a repeated decorative marker. Still check whether the marker communicates order clearly. A symbol that looks attractive in a short mockup may become confusing when the content grows or when readers need to distinguish one step from another.
Corner styling and text decoration gain finer controls
Corner shorthands combine border-radius and corner-shape settings. Meanwhile, text-decoration-skip-spaces controls whether decoration lines cross whitespace. These options target different visual details, so they should be tested independently rather than bundled into one redesign.
For reusable cards, compare the proposed corner treatment at several sizes and against the surrounding surface. For links, inspect complete phrases as well as single words. The visible result should remain understandable when text wraps, and a revised decoration should preserve the reader's ability to recognize interactive content.
Margin trimming needs the correct container context
Margin-trim can omit margins at the beginning or end of child content in ordinary block and multicolumn containers. The beta announcement explicitly excludes flex and grid containers from this scope.
An article-content wrapper would be a practical place to compare the behavior with existing spacing rules. Use a heading-first example, a paragraph-first example, and content ending with a list. Check adjacent sections too: removing a child's outer margin should not accidentally erase separation that the page structure still needs.
IMPORTANT: This announcement describes a beta release, not universal browser support. Retain a usable fallback and verify each feature in the browsers your template is intended to support.{alertWarning}
Daisuki's Take: What This Means for Web Designers
We would treat the beta as a focused testing opportunity. Cleaner declarations are valuable when they express a component's intended behavior more clearly, not simply because they are new.
For template creators, a small test collection can make adoption deliberate. Keep examples that show long content, narrow containers, and the fallback result, then use them to decide whether a feature belongs in production.
Our practical preference is progressive enhancement. The website should remain readable and usable without the experimental styling, while supported browsers receive the more refined treatment.
Sources and Recommended Links
- Chrome 155 beta | Chrome for Developers Official Blog
