*Summary:* border-shape (CSS Borders Level 4) lets authors draw an element’s border along one or two arbitrary basic shapes — circle(), ellipse(), inset(), polygon(), path(), shape() — instead of the usual (rounded) rectangle. A single shape is stroked with the border width; a pair of shapes fills the area between them; the background is clipped to the outer shape and border-radius is ignored while border-shape is in effect. This gives web developers styleable non-rectangular borders (badges, speech bubbles, stars, ticket stubs) without SVG workarounds or clip-path + nested-wrapper hacks, and keeps the border part of regular CSS styling (colors, backgrounds) rather than baked-in images.
Sampler: https://static.januschka.com/firefox/i-1982766/ *Bug:* https://bugzilla.mozilla.org/show_bug.cgi?id=1982766 *Specification:* https://drafts.csswg.org/css-borders-4/#border-shape *Standards Body:* W3C CSS Working Group (Editor’s Draft of css-borders-4). *Platform Coverage:* All platforms (Desktop and Android). *Preference:* layout.css.border-shape.enabled (default on in Nightly, off elsewhere). *DevTools Bug:* N/A — the longhand is inspectable and editable through the regular Rules view like any other CSS property. No dedicated tooling (e.g. a shape highlighter like the one for clip-path) is planned for the prototype; I can file a DevTools bug if that is wanted. *Extensions Bug:* N/A — no WebExtension-facing surface. *Use Counter:* css_border_shape (standard auto-generated CSS property use counter). *Standards-Positions Discussion:* https://github.com/mozilla/standards-positions/issues/1365 (open, no position yet). *Other Browsers:* - Blink: shipped (enabled by default since ~Chrome 147; `CSSBorderShape` is status "stable" in runtime_enabled_features.json5). Intent to Ship: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/69a582d1.050a0220.3c921b.08c1.GAE%40google.com - WebKit: no signal; position request open at https://github.com/WebKit/standards-positions/issues/625. *web-platform-tests:* https://wpt.fyi/results/css/css-borders/border-shape and the parsing suites in css/css-borders/tentative/parsing/ (border-shape-computed, -valid, -invalid). The current Gecko patches pass the full border-shape directory; interaction with outline, box-shadow, hit-testing and animation is not yet covered by the prototype and keeps FAIL expectations. *How Stable Is The Spec:* Editor’s Draft; the none | [<basic-shape> <geometry-box>?]{1,2} grammar and the geometry-box defaulting behavior are settled enough to prototype against, and the WPT suite (tentative) encodes the current consensus. Implementation status: parsing/computation and painting are up for review as D341191 and D341208. -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/e10c91e6-5459-4b9c-b80d-f14f5875543bn%40mozilla.org.
