Thanks for hiring me 😁
Posts by Una Kravets
Not that I know of 👀
Wooohooo! So happy to have you on the Chrome team! 🎉🎉🎉
First day at Google
Filming "What's New in Web" 2022
On the I/O Developer Keynote stage in 2025
7 years at Google today!? Wow time flies.
So much has changed but I'm still grateful to be doing meaningful work on a product that impacts billions of users with an awesome team 💙 This much hasn't changed 😊
If you’ve ever tried to build a data table with a sticky header and a sticky first column, you know the pain: the reality was that only one of both would stick.
A recent change to CSS fixes this: `position: sticky` now plays nice with _single-axis scrollers_.
DOMception
Real DOM content in a canvas: fully searchable, translatable, inspectable.
You can have forms, add WebGL effects & much more.
Imagine if this was a customizable select 🤯
A little WIP exploration (not finished) for a very exciting API.
github.com/WICG/html-in...
Wowowow epic talk by @kubekhrm.bsky.social about building liquid glass with SVG and CSS #ReactParis
Check out his post about it!
kube.io/blog/liquid-...
And a library coming soon 🎉
Super excited to kick off #ReactParis tomorrow! We're going to have some fun @bejs.bsky.social!
react.paris#schedule
No the spec returns only black or white. The original proposal allowed more colors like #222 but it was rejected to get it shipped and ensure a11y. I wrote a follow up on how you can achieve this though.
una.im/advanced-con...
I think the best option would be (as originally specified) the ability to test against multiple colors. This would be a bit more resilient
I think the challenge here is you can’t guarantee a11y since you’re selecting the colors. If it’s black or white only you can guarantee it
I don’t think so
Yeahhh clever but you need the custom prop
A vertical column of folders with labels on the right fanned out and curving towards the right.
Nice cards fanned out in a subtle arc.
Circular options with icons around another circular item in the center with a star icon.
Curious about custom <select>?
I wrote about some of my recent demos over at @css-tricks.com!
Take a look ✨ css-tricks.com/abusing-cust...
Timely :) I just wrote about color-contrast() landing crossbrowser soon
^ Cons: Firefox doesn't support style queries yet so browser support is limited for now (though it is an #Interop2026 feature!).
While contrast-color() only returns black or white, there are workarounds!
Register a custom property & you can use style queries for full color palette customization (test the contrast yourself!)
You can also use the contrast value inside color-mix() to make a color tint.
una.im/advanced-con...
Tomorrow I'll show you some contrast-color() hacks for better control over your color palette selection
contrast-color() is landing in Chrome 147, making it Baseline Newly Available in all modern browsers
It takes any color value and returns either black or white: whichever provides the highest contrast against the input
Works great with generated colors, state changes, etc.
una.im/contrast-color
+1, it's been discussed :)
It seems we can now customize the select element, right? right?!
Demo: codepen.io/t_afif/pen/P... via @codepen.io
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.