2026 want list (Interop 2026)
The Interop 2026 draft doc says proposals are going to be open through most of Sept. nothing final of course until announced but the time to start thinking more seriously about this is now https://github.com/web-platform-tests/interop/blob/main/2026/selection-process.md
26 Replies
is this a continuation of https://discord.com/channels/436251713830125568/1364233248913490004?
yep, yep thanks for linking.
Chrome now has experimental
border-shape (https://drafts.csswg.org/css-borders-4/#border-shape) implementation behind the "experimental web platform features" flag in canary: https://issues.chromium.org/issues/370041145 it's super early days so not much works yet. But stuff is happening.
firefox issue is open as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1982766 nothing for webkit yetTime to propose JPEG-XL for the fourth time, can't wait!
there has been some work on the rust implementation
Here's the github for the rust jxl decoder that Firefox has been asking for. https://github.com/libjxl/jxl-rs/issues/58 It's been worked on a lot this year. There's no release version yet and I don't know of any browser implementation testing either. But this is more progress then we've seen on this in years.
GitHub
tracking bug: stages · Issue #58 · libjxl/jxl-rs
blending chroma_upsample (-> chroma_upsample.rs) epf (-> epf.rs) from_linear (-> from_linear.rs) gaborish (-> gaborish.rs) noise (-> noise.rs) patches (-> patches.rs) splines (-&g...
i just feel like firefox isn't doing fuck all with this
they demanded a rust implementation - a language they originally created
and what do they do? get grumpy and don't touch the rust implementation until it's done, then they will think about may considering if there's the possibility of probably including this
at least, that's how i feel about this
one of the things that I have to remind myself of every once in a while is that the Mozilla we have today is completely different to the Mozilla we had pre 2020. From most reports that I've read they were really close to just completely dying as a company. Many of the things we know them for were spun off and are now separate (rust, MDN). While we might still think of these things as Mozilla they really aren't anymore. I'm not sure if there are any former Mozilla folks working on jxl-rs.
i mean, it's a bit of a dick move to demand a rust implementation and then ... nothing
they still use it for firefox
Yes I know, I track that.
It should be in a ready for integration state by the end of this year hopefully. Although integration itself is a tricky matter anyways, so realistically this misses this years interop.
Hopefully it will be good enough for integration into Chromium, but there wasn't any official statement from them and some of the people there have weird political stances. We will see.
I would like to see better WPT tests for progressive decoding and animation support.
They outsourced the development to the codec team at google, it is a pretty reasonable deal as something like this requires being an expert in a pretty specific area, and Mozilla with the recent layoffs doesn't have the people qualified for this from what I understand.
The fact that they did this is kinda funny though.
"hey, you, we want this written in a language we invented and use daily so we can add it to our browser ... but google and others have to implement it, not us"
Yeah and?
that's me impersonating mozilla to describe the situation, as a way to ridicule it
You are only ridiculing yourself by a statement like this.
don't feel like im being ridiculed 🤔
¯\_(ツ)_/¯
hopefully the implementation is done before 2026
planning on proposing at least
corner-shape and shape() this year. shape() seems more likely to get accepted for 2026. corner-shape seems more like a 2027 thing if i'm being honest but still good to get on the list this year to get another community signal for it.
because it was brought up in here at one point passing along that Jen Simmons is asking for feedback about -webkit-font-smoothing https://mastodon.social/@jensimmons@front-end.social/115051359883910788also posted on bluesky: https://bsky.app/profile/jensimmons.bsky.social/post/3lwp46vvcws2j
Jen Simmons (@jensimmons.bsky.social)
Do you use `-webkit-font-smoothing` in CSS? How do you feel about it? Would you miss it if it went away???
Bluesky
we need proper a/b testing with that
do you know if there's any tests for this?
if you mean web platform tests no there wouldn't be any because
font-smoothing was never added to a spec as far as I can tell. There was some talk about it on the old www-style list serve: https://www.w3.org/Search/Mail/Public/search?keywords=font-smoothing&lists=www-styleno, like a test to compare both with and without that property
maybe it could even be a poll
the MDN article has a screenshot of the smoothing difference for folks not on mac: https://developer.mozilla.org/en-US/docs/Web/CSS/font-smooth#examples honestly, I'm not really seeing the difference. But to be fair I couldn't tell the difference between round and squircle corners a few months ago and now I can spot that right away. Maybe one of those things that if the difference is pointed out it's easier to see?
it looks exactly the same to me
maybe back when this was originally being talked about the difference was more obvious?
maybe, i really cant say
Firefox is the first to 100% of the
<details> element tests 👍
it's good to see that firefox is still improving
webkit blog on
random() now in tech preview: https://webkit.org/blog/17285/rolling-the-dice-with-css-random/