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
188 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/very happy about that one making progress finally 😄
yep, very cool demos too. Although encouraging the use of 100 <div>s for a star field doesn't sit super well with me. This is the reality of what people do though.
was playing around with star shapes with
corner-shape. scoop 50% makes one and an inset squircle makes a fancier one. There's no keyword for inset squircle though so you'll need to use superellipse(-2) or some number between -1 and -2 (that could be randomized too I guess): https://codepen.io/jsnkuhn/pen/qEdKNKBdo you know when browsers will finally support
:empty with whitespace?ah that's cool. And yeah, the starfield is clearly done as a "everyone will understand this", but it's a bad to demo something people shouldn't do... The other examples they have are so much better.
seem like the conversation is still ongoing in the working group for
:empty: https://github.com/w3c/csswg-drafts/issues/1967
i remember this being proposed for interop in previous years. But the WG need to make a decision on this before anything can more forward. There's also the potential that one of the browser vendors just says "screw it we're tried of waiting" and implements something.
worth checking if there are standards positions listed for firefox and safari and if there are bugs open in the trackersi would think that this is a no brainer ...
a live stream vod of chris coyier going over the
random() blog post: https://www.youtube.com/live/agjJMAxPajQ?si=bDMR63jzKSKvMVXL&t=460Firefox's intent to ship for view transitions (i think this means Firefox 144?): https://groups.google.com/a/mozilla.org/g/dev-platform/c/JuDlPRWOFWY/m/5OjxV2Y-DgAJ
oh, nice
so... github finally supports WEBP images. congrats to github for getting right on that 10 years ago band wagon. Maybe they'll give AVIF support by 2035.... : https://github.blog/changelog/2025-08-28-added-support-for-webp-images/
Allison
The GitHub Blog
Added support for WebP images - GitHub Changelog
WebP image support is now available across github.com and GitHub Enterprise Cloud with data residency. Previously, uploading WebP images resulted in broken previews or forced users to download files to…
🤣 really?
last weeks meeting notes from the Interop committee seem to imply that the Sept 4th date for opening proposals is still on? Guess we won't know for sure until Thursday though: https://github.com/web-platform-tests/interop/issues/988
Firefox is officially experimenting with jxl-rs behind a flag: https://bugzilla.mozilla.org/show_bug.cgi?id=1986393
1986393 - land initial jpegxl rust code pref disabled
ASSIGNED (zondolfin) in Core - Graphics: ImageLib. Last updated 2025-09-02.
Along with a lot of other stuff of course, new Safari Technical Preview finally includes
scrollbar-color: https://webkit.org/blog/17324/release-notes-for-safari-technology-preview-227/WebKit
Release Notes for Safari Technology Preview 227
Safari Technology Preview Release 227 is now available for download for macOS Tahoe and macOS Sequoia.
how long has it been? almost 2 years?
how long has what been??
the jpegxl stuff
been about 3 years since Firefox and Chrome announced "removing" support. About 2 years prior to that they started initial work on implementing it?
3 years
wow
time flew
Interop 2026 Proposals are officially open: https://github.com/web-platform-tests/interop/issues
GitHub
web-platform-tests/interop
web-platform-tests Interop project. Contribute to web-platform-tests/interop development by creating an account on GitHub.
almost 50 proposals already and it's only been 3 days. Fair to say at this point that the community for sure recognizes Interop as important.
Don't forget to give the proposals you are interested in a thumbs up.
yeah, we don't need another "ie vs the word" situation
Surprised no
attr() yet , or text-box-trim (but there is one for margin-trim anything for
inherit() or whatever it was?can't imagine
attr() and text-box-trim aren't still coming. Wana say both have been proposed 3 years in a row.
can't say I remember an inherit() function?i remember seeing something about it in the spec
It is a part of https://drafts.csswg.org/css-values-5/#inherit-notation
That spec is still in the early working draft stage.
i knew i wasn't crazy, but google didn't give me anything
ahh, yeah we did look at that before. Comes from the same spec as
random(), random-item(), calc-size, interpolate-size. Hopefully a browser will pick it up and start experimenting.
As far as I can tell nothing in the webkit or mozilla standards positions repos yet for inhert(). Opening issues there is probably a good place to start to officially get it on their radars.
question for ya'll: do you think it would be wired/tacky if you saw an Interop proposal proposer give a thumbs up to their own proposal?in general, i see upvoting your own stuff as a desperate plea for someone else to agree with you, when nobody else does
like patting yourself on the back because nobody else wants to
but, considering the situation, i bet people upvote their own stuff
i doubt I'd even notice, but I probably wouldn't do it myself because I'd feel weird about it, lol
i can see why you'd do it though. The whole people are more likely to click on a reaction if it's already there vs having to be the one to open the menu and select it for the first time. So why not just get the ball rolling yourself maybe is the thought?
anyway, I have
shape() and corner-shape up so far. For now just going to sit and see what else comes in.that's a reasonable thought as well
yeah that's true, putting it in so that it's there to start makes sense.
Also, it's not like 1 extra reaction is going to sway things one way or the other (or, very unlikely anyway)
yeah, it's still ...
i wouldn't worry about it and just upvote, but would feel like i ate chewing gum while having peanuts
Still no attr() 😰
jxl-rs now has a 0.1.1 release version: https://github.com/libjxl/jxl-rs/releases
and there's another jxl rust decoder that I didn't know about that also has an alpha release: https://github.com/tirr-c/jxl-oxide
highlighting a proposal for SVG stroke-alignment, a thing I've been wanting forever: https://github.com/web-platform-tests/interop/issues/1074
GitHub
SVG stroke-alignment · Issue #1074 · web-platform-tests/interop
Description Being able to specify stroke on outside or inside a closed path could open up a lot of great designs and less hacks like avoiding paint-order or clipping/masking svg elements. If the pa...
we should probably have this in canvas as well
is that part of the svg spec?
The second one was the original rust one, but then that tirr-c guy was hired to work on the first one. Team at google decided that it is better to create a new one as a part of the libjxl project than develop that other one, for some reason.
stroke-alignment or stroke-align I want to say was originally part of SVG 1 and then for reasons unknown got booted to SVG2. Just took a look at the SVG 2 spec and it's not there again? The SVG working group doesn't exist right now so I don't know when it would have gotten changed....
found it annotation #6 under 13.5.1 : https://svgwg.org/svg2-draft/painting.html#SpecifyingStrokePaintthat is strangely interesting
so i guess there's another possible name then
stroke-position
here it is when it was part of the SVG 1 spec: https://www.w3.org/TR/svg-strokes/#SpecifyingStrokeAlignmentI made time to add it myself , although not certain I followed the outline for the proposal properly.
Interop 2026 Focus Area Proposal for advanced attr()
GitHub
Advanced attr() · Issue #1077 · web-platform-tests/interop
Description The attr() CSS function is used to retrieve the value of an attribute of the selected element and use it in a property value. ### Parameters The attr() function's syntax is as follo...
the proposal looks good to me. There really isn't a "correct" way to fill things out beyond starting with the "Focus area Proposal" template after clicking new issue. The most important thing seems to be that the
focus-area-proposal label gets added (which happens automatically if you use the template) so it gets moved over to the project tab once open proposals end.
10 days left for proposals. Wedesday Sept 24th, 2025 is currently listed as the last day.Good to know as I wasn’t sure I was putting the links for issues and dev interest in the right place- different posts added it in different places. And wasn’t sure what to use for the description so I just pulled from MDN. I’m still shocked it wasn’t added in the first ten days.
There are so many good ones I’ve upvoted (didn’t upvote my own btw 😆 I figure the post itself counts as my upvote) - does anyone know how many properties are usually focused on every year ? Is it a dozen or like 3?
in the past they've had something like 15-20 "focus areas". A focus area can be something specific like this year we've got
backdrop-filter and details element but also there's usually a generic "layout" category which it more general (flexbox and grid tests this year). There's also usually a catch all category called "Web Compat" where stuff goes that doesn't really fit into it's own category (things that have a small number of tests).Wow. Man, what a project. im so curious about the whole thing. How many people are on the interop team, what organization or entity heads it, where does the funding come to pay them, is the team comprised of engineers that work with the different browsers or do they do all the work then hand it off to the browsers in need, how to they keep everything synced and compatible to work with the different engines, is there data from past years like stats of what was focused on amd what was implemented and if so whats the percentage that was successful, and if not successful why did it fail, etc etc. To clarify not asking anyone like I expect all these answers. Just general wonderment into the ether 😆
This is a link to the 2025 dash board where everything is tracked but if you go down to the bottom you'll find links to previous years: https://wpt.fyi/interop-2025 (or you can just change the number in the url to past years)
the web-platorm tests github readme would be the place to start to find the other info: https://github.com/web-platform-tests/interop?tab=readme-ov-file#the-interop-project
played around a bit with anchor position this weekend. The oddbird polyfill has some basic support for
position-area now https://github.com/oddbird/css-anchor-positioningGitHub
GitHub - oddbird/css-anchor-positioning: Polyfill for CSS Anchor Po...
Polyfill for CSS Anchor Positioning. Contribute to oddbird/css-anchor-positioning development by creating an account on GitHub.
that's an odd name, but that's actually awesome
maybe it could be a nice #resources ?
speaking of anchor position, and a whole lot more, Safari 26 release notes: https://webkit.org/blog/17333/webkit-features-in-safari-26-0/
What I wonder, does it makes sense to file an issue that is specifically about concerns with dev tools?
It would be good if "Server-Timing" was supported as a HTTP Trailer! in browsers other Firefox, currently it is only supported as a header across the browsers, which is kinda useless
Guess I will just try to write about it and see if it is okay
initial thought would be that's is out of scope for interop because it doesn't have a spec with tests in the system but they did have "core web vitals" category this year which is the same kind of thing I guess?? They may have specifically made tests for that? Honestly though worst case response from the group is "we can't really do anything with that" but maybe the browsers have a look at it on their own?
Firefox just marked their "Implement CSS module scripts" bug as resolved: https://bugzilla.mozilla.org/show_bug.cgi?id=1720570
1720570 - Implement CSS module scripts
RESOLVED (dminor) in Core - DOM: CSS Object Model. Last updated 2025-09-15.
You are so dialed in to all the browser testing , bugs, releases - thank you for sharing! How do you keep up with it all ? Seems like there are so many places to monitor even if you get the digest from each. I tried last year to sign up for some google groups that were for different browser issues and it was too much for me to keep up with
your welcome. but i'm definitely not dialed into everything, that would be a full time job on it's own. Just the things I'm kind of interested in. I'm sure I miss a lot.
I just "vote" for alot of bug in the vedor bug trackers. if you're not aware, you can vote for bugs in the vendors bug trackers to get updates. it's how I knew about the CSS module scripts thing I just got an e-mail this morning about the Resolved status.
filed interop propsal for typed OM, maybe 4th times the charm: https://github.com/web-platform-tests/interop/issues/746
Good news for some long sought-after things that have been overlooked by Interop. Igalia will be working on MathML, text-box-trim, CloseWatcher and typed OM : https://www.igalia.com/2025/07/14/Igalia,-Interop-and-the-Sovereign-Tech-Fund.html
Igalia
Igalia, Interop and the Sovereign Tech Fund | Igalia
Igalia is an open source consultancy specialised in the development of innovative projects and solutions. Our engineers have expertise in a wide range of technological areas, including browsers and client-side web technologies, graphics pipeline, compilers and virtual machines. We have the most WPE, WebKit, Chromium/Blink and Firefox expertise f...
This one still kindof haunts me 🙃
https://github.com/w3c/csswg-drafts/issues/1659
GitHub
[css-grid] Control size of individual gutters independently · Issu...
Thread starting here asks for the ability to manually control gutter sizes, so they can be different sizes in different spots. Right now, the only way to do so is to create it as a track, and then ...
yeah, i remember being pretty excited about this one too....
Seems like the working group is dealing with at least the first bit of
gap-decoration first (Different gaps sizes is marked as css-grd-3 and decoration is ccs-grid-2). Which there's now a test implementation of in chromium so maybe they can get back to different gap sizes sometime???I hope so.
The most common use case for me would be to shrink the gaps between fractions and grid-columns to 0 when templating with grid and no extra wrapper. Abstract:
1fr-12columns-1fr
The issue is that those fraction gutters remain, even if the fraction's size is 0 – so the remaining gutters add to a page's inline-padding causing horizontal overflow.approaching 100 Interop proposals with about a week to go
anything still missing from the list that peeps think should be there? https://github.com/web-platform-tests/interop/issues?q=is%3Aissue%20state%3Aopen
So any way to filter by which got upvoted the most ? Or they have to go through one by one and look at the reactions ?
Unsurprisingly #1 is once again, by a long shot (almost 150 ahead of the next closest), is JXL. https://github.com/web-platform-tests/interop/issues?q=is%3Aissue%20state%3Aopen%20label%3Afocus-area-proposal%20sort%3Areactions-%2B1-desc
news on #4 Temproral API this morning. Chrome has an intent to ship for 144: https://groups.google.com/a/chromium.org/g/blink-dev/c/s58GKzoQZFg
jpegxl is desirable to a lot of companies
imagine this: you shave 20-50kb per jpeg image, with 0 quality loss
just by re-packaging it from jpeg to jpegxl
the huge amount of space and money you can save with this
and with a good cache system, you can re-encode the jpegxl to jpeg on the fly, if needed
also, it's an awesome format all around
and google did it dirty
no wonder it is #1
Just realized I didn't say but proposals are now officially closed. Here's the rough timeline of what happens next:
https://github.com/web-platform-tests/interop/tree/main/2026#timeline
3 weeks for proposals and about 3 months for selection
😰
are there that many proposals?
yep, there are around 150 proposals again this year. They also have to go over anything that needs to be carried over from the previous year.
Looks like the most obvious one that will need to be carried over is anchor position. Firefox doesn't seem to have even touched it yet? Unless they've been working behind a flag so it's not showing up on the test score??
that is a very solid reason for taking so long
also been wondering with 3 multi trillion $ companies behind the browsers how much approval from higher ups has to play a roll
that has an influence
a big one
and also this
What did Google do,
google covered it's eyes, pushed it's fingers into it's ears and went "lalalalalalalalalalala"
then removed jpegxl from google chrome
this was the explanation for removing it that got folks upset. Note that this was after about 2 years of experimenting with it and tons of previous messages in the same thread with glowing support for the format from giant tech company, after giant tech company, after giant tech company: https://issues.chromium.org/issues/40168998#comment85
so I posted too soon about anchor position Firefox shot up from about 15 to about 60 yesterday:
yikes, someone trying to use the current state of CSS
image-rendering:
that is disgusting
something I completely missed in the enormous Safari 26 release notes. Scroll driven animation support: https://webkit.org/blog/17333/webkit-features-in-safari-26-0/#scroll-driven-animations
That leaves just Firefox without support. So maybe this is low hanging fruit for Interop 26.
a reddit AMA with Firefox leadership October 6th: https://www.reddit.com/r/firefox/comments/1ntui9x/upcoming_ama_with_firefox_leadership/
i bet one of the most common questions will be about google
looks like they did this last year as well: https://www.reddit.com/r/firefox/comments/1de7bu1/were_the_firefox_leadership_team_at_mozilla_ama/?chainedPosts=t3_1d9guev
W3C new logo... i guess. Maybe i'm just not awake enough to get it???: https://www.youtube.com/watch?v=fnaXvtnP6s0
W3C
YouTube
W3C unveils its new logo
At the occasion of the World Wide Web Consortium’s 31st anniversary, we are launching our new logo. This video is about our strengths and the values that we stand for. We bring together worldwide stakeholders. Together we develop open standards for a World Wide Web that connects and empowers humanity. New logo, same mission and commitment: mak...
the old one was definitely pretty dated... but I'm surprised they felt the need to hire an agency for what could have simply been switching to a sans-serif or something, lol.
The whole promo video reeks of agency work that's more there to promote it to the stake holders than it is to the public. The whole "we are" and "we champion" thing is them putting all the key words they had during their meetings to make it look like they listened 😅
At least the old one I could read and know what it was... the new one, at best, looks like a fancy W³ ... and really, the W isn't that much of a W.
At the same time, I don't really care? lol. It looks more modern at least 😄
basically, keyword vomit on top of a font change?
here's a link to the logo itself if you don't wana watch the video: https://www.w3.org/assets/logos/w3c-2025/svg/w3c.svg
it looks like a weird ∞ with a vestigial ³ growing on the side :/
it does not look like a w
a reason that maybe they didn't go with the w to the 3rd power thing directly might be to avoid being too similar to the W3Schools logo?
oh, I forgot w3schools did that... now it feels even more lazy 😅
🥁
that's 80% of the work done
I actually seen it like a month or two ago, it was on their design system website
https://design-system.w3.org/templates/landing-new-logo-v2.html
here
TBH I like the old one better
There you don't have to spell W3C two times just because the logo is completely unreadable, and unmemorable too!
oh, yeah, the old one is a lot better
there's a blog post explainer: https://www.w3.org/press-releases/2025/new-logo/
W3C
The World Wide Web Consortium (W3C) adopts a new logo to signal pos...
W3C is rolling out a new logo, following W3C’s formation in 2023 as a non-profit, public-interest organization, and the recent release of strategic objectives to support W3C’s roadmap.
I'd make a video on this, except I don't really want to be negative... we have enough of that going on in the world today... as long as the people who commissioned it are happy, I guess 😄
line-clap finally looks like a realistic possibility for 2026: https://github.com/web-platform-tests/interop/issues/1029#issuecomment-3258884685GitHub
CSS
line-clamp property · Issue #1029 · web-platform-tests/interopDescription CSS property that will contain text to a given amount of lines using the line-clamp property. When text-overflow: ellipsis is included, it will end with ellipsis. Specification https://...
😮
finally
and next, hopefully ... this
I checked on that last week. No one proposed
image-rendering this year. Last year it got proposed by an Apple rep: https://github.com/web-platform-tests/interop/issues/875 (specifically the crisp-edges value). The pixelated value actually looks really well supported cross browser. So the dev on that scene shot probably didn't really need to do all that work. Not sure how much of that was just legacy auto-prefixer stuff.mostly auto-prefixer
this is what auto prefixer gives me going back 2 versions (and... 200 versions). So there was something else going on there too:
it's missing the old value, before
pixelated was added
the optimizeSpeed was what chrome used for a long while
optimize-contrast was probably a value added a while ago, before pixelatedcrisp-edges is only not supported in chromium because I guess there's still some confusion about what crisp-edges is suppose to do? This is a conversation from 10 years ago but it still seems to be relevant unfortunately: https://github.com/postcss/autoprefixer/issues/367#issuecomment-72149808GitHub
Support image-rendering · Issue #367 · postcss/autoprefixer
Specs(CR) http://dev.w3.org/csswg/css-images-3/#the-image-rendering The standard value: auto crisp-edges pixelated The old value optimize-contrast’ = ‘crisp-edges’ Changed the ‘optimize-contrast’ v...
here's the chromium bug if anyone wants to +1 it. although 41 is already a high enough number that you'd think they'd be looking at it... : https://issues.chromium.org/issues/41073066
latest Safari tech preview notes. Honestly not much here. Nice to see a handful of SVG things being worked on though: https://webkit.org/blog/17447/release-notes-for-safari-technology-preview-229/
cupiq's stuff will finally work on safari
or did it work already?
was that the fancy svg filters stuff?
yes it was
then nope nothing in TP229 to do with SVG filters. But you'd think with all the excitement about "liquid glass" from apple that those would be a higher priority than they were before?
to be honest, i would expect improvements to make sure the liquid glass doesnt work like ass
they are really milking it in all devices, so, why not help devs to infect their websites with this rejuvenated windows vista look?
Chrome intent to prototype for CSS form controls level 1: https://groups.google.com/a/chromium.org/g/blink-dev/c/n1NsO0N_tO4/m/ruZbb1qsAgAJ
here's the chrome bug to follow: [css-forms-1] Customisable Form Controls https://issues.chromium.org/issues/450139531
webkit: https://bugs.webkit.org/show_bug.cgi?id=278084
a Firefox meta bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1982781
Was looking around at some of the new form styling stuff and came across this old webkit psuedo:
Had to look it up on MDN to make sure it was real. https://developer.mozilla.org/en-US/docs/Web/CSS/::-webkit-meter-even-less-good-value
(@firefoxdevtools.bsky.social)
As an experiment, we (the Firefox team) wanted to try a new way to get feedback on which Interop proposals matter most.
So, here's a web app where you can rank the proposals you care about, giving us data we can use when reviewing which ones to champion.
interop-rank.jakearchibald.com
-# Interop Feature Ranking Rank the web platform features you care most about
Bluesky
For anyone who might be a little leery on the feature ranking thing because it's a bit weird that it's up on Jake's personal site and not an official Mozilla server. This is really a thing. Here's the conversation about it from last weeks interop meeting for confirmation: https://github.com/web-platform-tests/interop/issues/1192#issuecomment-3366269663
the long sought after ability to use CSS var() in external .SVG is getting spec-ed: https://drafts.csswg.org/css-link-params/#setting-url
chrome bug: https://issues.chromium.org/issues/41482962
firefox bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1812163
nothing for safari yet that I can find
poked around with anchor position again this weekend. Every time I go back to it I find something else that makes things easier to write. Only thing that's missing for me right now is an
anchor-gap type property.seems to be planned for anchor position v. 2: https://github.com/w3c/csswg-drafts/issues/10396
GitHub
[anchor-position] CSS anchor position gap · Issue #10396 · w3c/cs...
After a short Q&A with Tab Atkins-Bittner we discussed the possibility of adding anchor-position-gap to elegantly add space between the anchor and the element attached to it proposition to the ...
w3c did another blog post (https://www.w3.org/blog/2025/w3c-logo-refresh-more-than-a-cosmetic-change-a-small-step-towards-durable-and-sustainable-success/) on the new logo and corporate talking point changes..... What I find interesting is that they make some small changes to the old logo back in 2022:
weird ... some places are pointy now, others are round now
interesting
looks like the new w3c logo doesn't have a dark mode version? Maybe that's still to come? It's just gleaming white on the editor draft specs.
Also that h1 needs really needs a
text-wrap: balance; or pretty maybe
chrome intent to prototype for inherit(): https://groups.google.com/a/chromium.org/g/blink-dev/c/nCUNGmfAOMU/m/YOCfBQV6BwAJ
😮
yes yes yes!
article on inhert() in components: https://www.alwaystwisted.com/articles/making-context-aware-components
Firefox intent to ship for
Summary from firefox's intent to prototype (https://groups.google.com/a/mozilla.org/g/dev-platform/c/3Gk5csjxi1s/m/WcRhlTixCAAJ)
text-autospace: https://groups.google.com/a/mozilla.org/g/dev-platform/c/69xH8RcOULw Seems pretty niche i'm sure there are folks who will be happy to see this finally becoming fully cross browser.Summary from firefox's intent to prototype (https://groups.google.com/a/mozilla.org/g/dev-platform/c/3Gk5csjxi1s/m/WcRhlTixCAAJ)
Summary: text-autospace automatically creates small spacing between characters of different writing systems (e.g. between Latin scripts and Chinese or Japanese scripts), enhancing readability in multilingual content.ok, maybe scratch the whole "good cross browser compatibility" thing. Seems that 3 values are consistent and 6 others aren't: https://developer.mozilla.org/en-US/docs/Web/CSS/text-autospace#browser_compatibility
Jen Simmons (@jensimmons.bsky.social)
We’ve been busy over here. For those asking about “stable” — yes, the work that’s currently in Safari Technology Preview will land in stable. Yup.
Bluesky
yep, yep its the sprint to the end of the year for Interop 2025: https://wpt.fyi/interop-2025
unfortunately it look like Firefox isn't likely to get anchor position in before the end of the year. I'm sure it will just get rolled over to Interop 26.
Firefox closed a bug over night related to the
shape() function. Not sure if this is just a one-off or the start of something.
https://bugzilla.mozilla.org/show_bug.cgi?id=1917128Firefox 144 stable is live with, among many other things, single-page view transitions
https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/144
MDN Web Docs
Firefox 144 release notes for developers (Stable) - Mozilla | MDN
This article provides information about the changes in Firefox 144 that affect developers.
Firefox 144 was released on October 14, 2025.
oh, forgot to mention this makes view transitions baseline across all 3 big engines. (Well if you still consider FF to be a big engine. Which is getting harder and harder to argue as time goes on...).
worth mentioning that the Interop 2023 stuff should now all be either widely available or getting there soon (30 months is the marker - 2 1/2 years). So time to use math functions, color spaces, registered custom property, has, prefix-less masking, etc without much worry. https://wpt.fyi/interop-2023
Chromium prototyping interation Composite: https://groups.google.com/a/chromium.org/g/blink-dev/c/I7YQiIleH_o/m/_1B9JnCMCAAJ
Summary: The iterationComposite property controls how successive iterations of a CSS animation combine with each other, allowing developers to specify whether each successive iteration is calculated independently ("replace") or is accumulated with the final value of the previous iteration ("accumulate").From chromium as well -
Web-Facing Change PSA: Tune border-radius correction to better match circles/ellipses:
https://groups.google.com/a/chromium.org/g/blink-dev/c/MtaFEiEtgbM
This is about maintaining the expected shape with larger box-shadow values. Here's the csswg thread:
https://github.com/w3c/csswg-drafts/issues/7103
Intent to prototype & ship: CSS contrast-color() function for Firefox 146 (already in Safari 26) : https://groups.google.com/a/mozilla.org/g/dev-platform/c/vP92yf-V2iw/m/gkMDgUHsAAAJ
spec link: https://drafts.csswg.org/css-color-5/#contrast-color
Chrome adding text-justify to control whether text-align: justify; justifies per word or per character.
https://chromestatus.com/feature/5079678972985344
already if Firefox all the way back to v 55 (aug 2017)
there's a survey on the naming of the masonry layout. Just for potential non "masonry" options: https://github.com/w3c/csswg-drafts/issues/12022#issuecomment-3452974749
chromium Intent to ship: CSS caret-shape https://groups.google.com/a/chromium.org/g/blink-dev/c/a_1mwtfo8tQ/m/fddRQW7QAwAJ
Finally an Intent to Ship from chromium for "side-relative syntax for background-position-x/y longhands" https://groups.google.com/a/chromium.org/g/blink-dev/c/PSDj9jEOm0s
This has been in Firefox since 2016 and Safari since 2022. Interesting, was also added to Edge in 2015 (so they were first) but lost when edge moved from EdgeHTML to blink.... https://caniuse.com/mdn-css_properties_background-position-x_side-relative_valuesIt was in IE9 too
Wild
wait, this wasn't a standard?
🤯
it was a standard chrome just never supported it
so, chrome was wrong
that's good to know
for some reason the chrome engineers just don't tend to jump on css background/border related stuff as much as everyone else. I don't know why this is. This is why I was so surprised when they jumped at implementing
corner-shape. I honestly thought they'd be the last not the first.probably because it's a ton of work for not much return
i hear this sort of thing alot. Something like "background images just don't get much use" but here's the stats for
background-image. 80% of page loads in chrome use it. I don't know why the general talking point is so divorced from reality.
https://chromestatus.com/metrics/css/timeline/popularity/25my point wasn't about the usage
my point was about it just not being something that is very visible or that many people will notice
That's the thing with standards, it doesn't matter what you think is important. So they should just implement stuff as it comes out
it's chrome: they do whatever the fuck they want, like how ie did
Chrome does what they want to a degree. But the difference between them now and IE back in the day is that Chrome kinda does what they want but also they document it and put it in front of the working groups. In reality some of those chrome people are also on the working group so it's kind of a gray area thing.
Igalia video about whats going on with MathML in webkit: https://www.youtube.com/watch?v=Agetsr6yJ3I
Igalia
YouTube
MathML in WebKit 2025 (WebKit Contributors Meeting)
Fred Wang gives an update on MathML and plans
Lea Verou is doing a pole about syntax options for multiple borders. Both look to only be open for 2 days so drop in a response asap if you're interested in participating:
mastodon: https://front-end.social/@leaverou/115482600983968371
x/twitter: https://x.com/LeaVerou/status/1985123158370680869
Safari 26.1: https://webkit.org/blog/17541/webkit-features-for-safari-26-1/
lots of anchor position updates and... CSS Relative units in SVG?
Relative units in SVG As part of our most recent efforts on quality, WebKit for Safari 26.1 refactors the way the rendering engine handles CSS Units. This results in giving the SVG engine easier access to relative units, adding support for certain units inside SVG files for the first time. These units include rem; viewport units: vh, vw, vmin, vmax; typography-relative units: rlh, ic, cap, and container query units: cqw, cqi, cqmin, cqmax.I'm hoping Webkit posts a follow up blog post on the CSS units in SVG thing cuz i'm honestly having trouble picturing how this would work. Did a quick ctrl-f in the SVG1 and SVG2 specs and didn't find any reference to this so i'm not sure where it came from. I guess i could have just missed it though.
maybe they will be supported in css only?
Chromium removing the flag for the Temporal API in v144: https://groups.google.com/a/chromium.org/g/blink-dev/c/s58GKzoQZFg
That just leaves Safari. It's in TP for them though so probably soon? This feels like even more of a lock for Interop2026.
Safari 26.2 beta release notes. This is a big one: https://developer.apple.com/documentation/safari-release-notes/safari-26_2-release-notes
Apple Developer Documentation
Safari 26.2 Beta Release Notes | Apple Developer Documentation
Released November 4, 2025 — 26.2 beta (20623.1.12)
this weeks Codepen challenge is to play around with
shape() or corner-shape not much there but honestly don't know how many folks usually participate: https://codepen.io/tag/cpc-css-shape
Firefox intent to prototype and ship Navigation API for 147 (this is on Interop 2025): https://groups.google.com/a/mozilla.org/g/dev-platform/c/2U3cwQgCWBY
If i'm seeing this right that should make it baseline
will also be in Safari 26.2: https://developer.apple.com/documentation/safari-release-notes/safari-26_2-release-notes#Web-APIa relatively short (25min) talk on the Temporal API from Igalia: https://www.youtube.com/watch?v=5Q5vq-my6_k
Igalia
YouTube
Temporal: The Curious Incident of the Wrong Nighttime
This is the story of how I almost spent a night on the street — because of JavaScript's Date object! We'll dive in and try to understand why that happened, and how to prevent it. Luckily coming soon to a browser near you is Temporal, the JavaScript built-in API that makes this kind of mess-up a thing of the past.
Slides available at: https://...
This weeks Chromium only codepen challenge is to play around with custom selects:
https://codepen.io/challenges/2025/november
https://codepen.io/tag/cpc-custom-select/
Firefox 145 released yesterday: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/145
MDN Web Docs
Firefox 145 release notes for developers (Stable) - Mozilla | MDN
This article provides information about the changes in Firefox 145 that affect developers.
Firefox 145 was released on November 11, 2025.
It now features compression dictionary transport support! Although not sure if it is in stable, but it was added in 145 beta. Allowed only for HTTPS connections for some reason though...
gotta be honest had never heard of this. Doesn't seem to be on the 145 post and looks from the bug (https://bugzilla.mozilla.org/show_bug.cgi?id=1918013) that they've backed the work out at least once from problems. Last post mentions 145/146. So maybe not yet???
1918013 - Support <link rel="dictionary" href="...”>
RESOLVED (rjesup) in Core - Networking: Cache. Last updated 2025-10-15.
here's the meta bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1882979
Safari TP 232 mostly bug fixes: https://webkit.org/blog/17601/release-notes-for-safari-technology-preview-232/
WebKit
Release Notes for Safari Technology Preview 232
Safari Technology Preview Release 232 is now available for download for macOS Tahoe and macOS Sequoia.
Firefox "Intent to ship: CSS Module Scripts" for 147 https://groups.google.com/a/mozilla.org/g/dev-platform/c/ynzRS-tLvmU/m/FJZa1AoDAwAJ
Oh! That's cool
Someone made a tailwind
corner-shape plug in: https://www.npmjs.com/package/tailwindcss-corner-shape@Chris Bolson made an in-browser corner shape generator !
https://www.corner-shape.com/
CSS corner-shape superellipse() generator
A CSS corner-shape generator for the superellipse() function. Create your own corner shape with the superellipse() function and copy the code to your project.
Chromium "Intent to Prototype: Media element pseudo-classes"
https://groups.google.com/a/chromium.org/g/blink-dev/c/FqxaR-oQQ6c/m/qTjQjn5PAgAJ
Summary The :playing, :paused, :seeking, :buffering, :stalled, :muted, and :volume-locked CSS pseudo-classes match <audio> and <video> elements based on their state. There is already an implemention of :playing and :paused behind the CSSPseudoPlayingPaused runtime-enabled feature.
oh! finally! nice nice nice nice!
corner-shape currently intended to be in tailwind 4.2: https://github.com/tailwindlabs/tailwindcss/pull/19298I'm not sure of what to think about that
it's tailwind
just keep the same opinion and you will be right
I guess I don't know much about how they decide these things but i find the classes they are talking about very strange. They're say it'll be
.rounded-xl .corner-squircle why not just .squircle-xl or .notch-s cover it all in one?Because that would be too much abstraction xD
Tailwind is the leakiest of abstractions, they basically have a one to one mapping for all properties
the difference here is that
corner-shape on it's own doesn't do anything. It has to be paired with a border-radius value to function at all. They really are a pair.
dev updates on corner-shape as long as were talking about it:
Chromium - the live implementation is good enough for most use cases. They are still working out edge cases. For example they're currently looking at whether there should be a miter limit when large outset box shadows on large value concave corner shapes meet.
webkit - they are officially listed as positive on the property and have done some prep work for it but no implementation yet. My guess is they are looking for the time to prioritize. Potentially waiting to see what chrome is doing with the edge cases before starting?
Chromium bug [css-anchor-position] Let more pseudo-elements have implicit anchor elements (https://issues.chromium.org/issues/408223892) is marked as fixed. This is the one that makes, among other things, :before and :after implicitly anchored to their parent. So you won't have to give them the anchor-name/position-anchor properties anymore.Wanted to point out a new thing on caniuse that I haven't seen anyone mention yet. There's a new little thumbs up link to the right of some listing titles. Seems like the baseline people are trying to come up with an official place to collect developer sentiment. It links to a
web-platform-dx / developer-signals github repo.
Here's the full repo link: https://github.com/web-platform-dx/developer-signals/issues
GitHub
web-platform-dx/developer-signals
Tracking web developer signals for features. Contribute to web-platform-dx/developer-signals development by creating an account on GitHub.