They're also working on a menu element!
05.03.2026 19:53
👍 3
🔁 0
💬 1
📌 0
They're also working on a menu element!
Open UI has been working on speccing out the focusgroup attribute: a declarative way to support roving focus & add keyboard nav to composite widgets like toolbars/menus
We'd love your feedback!
Learn more & see open questions: developer.chrome.com/blog/focusgr...
H/t to Edge folks for prototyping
I think it’s also great to just be able to iterate faster. We often will release small incremental changes and features that may rely on one another.
I’m sure there was! I don’t personally know what the official reasoning to formally institute this change was, but as someone who’s often waiting for features to go from beta to stable because of the release cue, I welcome it :)
That wasn't the case when you had something like a CSS rename or behavior change since it wasn't a security issue. If you miss a branch cut for a new feature by one day you don't have to wait an entire month now to land it.
I don’t think this will make a huge difference for feature timelines, but it will improve bug fix landings and just make the browser more nimble
Chrome is moving to a 2-week release schedule!
(previously 4 weeks)
developer.chrome.com/blog/chrome-...
🤷♀️ it was resolved in the WG to do this behavior
I don't know if I love it either because there are other (different) side effects, but in this case think about the real-world scenario and I would probably say it's the more expected option.
This looks like it is working as intended. There was a change to the implementation in 135 to respect the most recent position based on scroll. In your demo, the most recent accurate position is preserved.
chromestatus.com/feature/4710...
It depends (is always the answer)
Inline I don’t find it improves the UI but sometimes if I have a list of mixed resources I might indicate with an arrow icon.
Officially shipping in Chrome 147 🎉
Oh man that would have been a better title: reshaping css with border-shape
I've been experimenting with an upcoming CSS feature called border-shape lately.
It's really cool what you can do with it: lots of practical applications + it opens a lot of doors for non-rectangular UIs!
Try it in Canary w/experimental web platform features on, & read more:
una.im/border-shape
Yea I agree with you that it feels weird and should paint to the border-box, which I expect to be the new border-shape edge. The insets aren’t a problem but it’s the extrusions. I gave this feedback
(Linked in the post, sorry)
See the linked issue ^
Disco wouldn’t tolerate sunglasses and a Hawaiian shirt 😆
Omg yes the flower
I don’t know how you would polyfill this outside of using clip path as a fallback and progressively enhancing the borders/outlines/shadows etc. you could also use corner-shape for some of the simpler ones.
I've been experimenting with an upcoming CSS feature called border-shape lately.
It's really cool what you can do with it: lots of practical applications + it opens a lot of doors for non-rectangular UIs!
Try it in Canary w/experimental web platform features on, & read more:
una.im/border-shape
This is shipped in Chrome, no current blockers for it to land crossbrowser either
Today we announce the following speakers:
- @patrickbrosset.com (Microsoft)
- @una.im (Google)
- and @nerdy.dev (CSS)
See our full line-up at cssday.nl
Element-Scoped View Transitions are gonna be **SO GOOD**
There’s still some details to settle, but the main thing is there: run VTs on a subtree of the DOM, allowing parallel VTs.
And with `view-transition-scope` you can limit the scope of `view-transition-name` values, allowing VTs to be nested.
For background-opacity, why not just set the background to an alpha color value to make it semi-transparent? Or use relative color syntax to do that?
Yes I was also sad to see it not make the list but hopefully next year
Oops missed a couple of things like contrast-color() and shape() <-- which is a great precursor to things I'm looking at right now like border-shape
#Interop2026 is here!
Lots of new CSS coming your way:
- style queries
- anchor positioning improvements (already crossbrowser)
- advanced attr()
- popover & dialog improvements like lightdismiss
- scroll-driven animations
- better scroll-snap capabilities
wpt.fyi/interop-2026
Yes, it was just resolved last week in the CSSWG to be added to the spec. That means we can ship it! I think there's some more work to be done but I don't have a timeline
Yesss the gap is nice too!
