I'm going to be hosting a session at TPAC next week in Dublin to have an open discussions on how browsers could help with atproto, activitypub, lws, indieweb, more specifically with identity!
www.w3.org/events/meeti...
I'd love to see you all represented there, remotely or in person!
@thisismissem.social@divy.zone and I recently went through an exploration of how the browser can help you login to websites with atproto accounts.
We recently presented to the FedID CG and here is a sneak peek in case you couldn't join!
This is early but we'd love your input before we go too far!
Did you know the State of HTML 2026 survey is currently open? Go take it and brush up on new (and old) browser APIs!
survey.devographics.com/en-US/survey...
✍️ Just published a new post about my most-anticipated CSS proposals from Interop 2027!
If you’re not familiar, the Interop project is a collaboration between browsers to pick shared focus areas. There’s *so much* good stuff this year, it was hard to pick just 10!
Happy World Browser Day!
I've long used "long live the web" as my motto/tagline, so today I published a blog post explaining what this phrase means to me: longlivetheweb.org/not-a-manife...
@dontcallmedom.eurosky.social I won't be able to attend TPAC in person and I know I missed the Oct 8 deadline, but would it make sense to propose a session for Thu/Fri still?
Chrome 155 adds support for JPEG XL (.jxl) → goo.gle/4yYpSjW
Expect 30-50% smaller file sizes than traditional JPEGs, native HDR, progressive rendering, and lossless JPEG transcoding.
Under the hood, Chrome uses jxl-rs, a pure Rust decoder built for maximum memory safety and performance.
Did Ukrainian drone strikes really silence Russia's social media bots? (No)
A real Cloudflare chart fueled a viral story ab MAGA and AfD accounts going quiet. But the evidence doesn't support the rumor.
I wrote about bots, vibes, & what we've lost as platforms have shut down tools & data access.
I reposted a claim about bot activity on X which I wanted to believe. Now reposting the correction which is not as fun, but the required penance for being wrong.
So there currently a raging debate on X, Bluesky & other platforms where people are using a drop in Cloudflare's YandexBot traffic to claim that right-wing online engagement is falling. radar.cloudflare.com/bots/as13238...
That conclusion doesn't follow from the data.
Going through the Interop list of features interop-rank.fxdx.dev and selecting and ranking the ones I want to see across browsers in 2027.
I chose 15 features.
At the top of my list are #HTML#a11y features `focusgroup`, ariaNotify(), `headingoffset` and `headingreset`.
What do you want us to work on in 2027?
Here's a web app where you can rank the Interop proposals you care about, giving us data we can use to prioritise feature development.
interop-rank.fxdx.dev
aamtest: Testing accessibility in WPT
blogs.igalia.com/mrego/aamtes...
This blog post covers the work @igalia.com has been doing to add a new type of tests in WPT, which allow testing the platform accessibility APIs directly.
Thanks to NLnet Foundation for sponsoring this work.
I’ve spent the better part of the last 2 years both using coding models and trying to help these models deliver higher quality code and I honestly could not agree more with Zach here… www.zachleat.com/web/ai-websi...
The "no steps back" is, in my opinion, what sets atproto apart from everything that came before it.
I use it too for much of my work in browsers too, under a different name: user behavior / developer backwards compatibility.
It comes at a massive cost, but I think is a powerful guiding principle.
ah damn, RIP Margaret Hamilton.
she took safety-critical software engineering seriously, and got people to the moon and back.
news.mit.edu/2026/margare...
Introducing Iris-AVIF, a better AVIF encoder & the best image encoder in the world:
halide.cx/blog/introdu...
Iris-AVIF offers up to >21% better compression than libaom, the reference AV1 encoder with image-specific tuning.
#av1#avif#jxl
Remember Internet Explorer’s “Page Transitions”?
Well, they’re back, thanks to the View Transition API!
→ Blog post: brm.us/page-transit...
→ Demo site: page-transitions.style
The project leverages IE’s meta tags so browser support is not limited to Modern Browsers™ but also includes IE 5.5–8.0 😆
Today marks three years since the terrorist attacks of 7 October in Israel.
We honour the victims and stand with the families who still carry the heavy weight of grief.
We remember the young lives cut short at a music festival. And the long ordeal of the hostages.
You don't have to think JPEG XL is the best format, or plan to use it, to understand that we all benefit when browser vendors are responsive to developer feedback. I'm sorry it took this long in Chromium, and while I'm unlikely to use this format in my own work, I'm happy we're adding options.
JPEG XL shipped in Chrome 155 today, try it out!
Huge kudos to Luca and team for getting this done. Image codecs are cool in so many levels, and I'm super impressed by the people who make that magic happen.
developer.chrome.com/blog/jpeg-xl...
JPEG XL shipped in Chrome 155 today, try it out!
Huge kudos to Luca and team for getting this done. Image codecs are cool in so many levels, and I'm super impressed by the people who make that magic happen.
developer.chrome.com/blog/jpeg-xl...
Developer Signals: shape what browsers build next. Rick Viscomi made a tool to browse upcoming web features and Interop 2027 proposals, vote with GitHub, and share use cases that go straight to browser vendors. #interop#browserdeveloper-signals.dev
GitHub just finished ripping styled-components out of github.com. Result: 55% less time to server-render a page, 25% faster component init.
CSS-in-JS makes you pay for styles twice: collecting them on the server, running JS on the client.
Static CSS is *always* more efficient.
Ship CSS.
GitHub.com has fully moved off CSS-in-JS to CSS Modules, resulting in 55% less server-side render time and 25% faster component init.
https://github.blog/engineering/architecture-optimization/improving-site-performance-by-shipping-more-css/
Always nice to do updates like this one 😊
Yes, CSS `light-dark()` with `<image>` values is now available in all major browser engines.
Check brm.us/light-dark-i... to get the details.
Welcome to the new PLC Organization @plcred.org
“a small Swiss Association (‘Verein’) which provides open network identifier infrastructure. It serves as a neutral steward for the Public Ledger of Credentials (PLC) system” plcred.org
Hello World from the PLC organization (plcred.org)!
The org was soft-announced back in March at AtmosphereConf. We've been working through logistics step by step and now have a public web presence we can point to.
🆕 Customize MDN's browser compat tables!
Press ⚙️ Settings on any compat table to choose which browsers and engines you see, and hide the ones you don't need.
Your picks are saved in your browser.
Try it 👇
developer.mozilla.org/en-US/docs/W...
Took a bit of inspiration from npmx and added a chart to developer-signals.dev showing total upvotes over time
This one's for the Temporal API. I love how you can see little surges in developer interest, first in December and again this month.
This is the best explanation of the interplay of specs, tests, and implementations that I've read.
The point of both specs and tests is interoperable implementations, but that doesn't mean that implementations are always right when they agree.
My colleague @atbrakhi.bsky.social wrote a nice, cleverly titled post based on a very short exchange we had on Instagram the other day...
www.atbrakhi.dev/blog/browser...
I would take it one step further. I think that if two implementations agree on something, it's irresponsible to change it without first considering the shortest path to interop. "The spec says so" is not a good enough reason without that path.
In the end, often a combination of changes across specs, tests, and implementations are required.
When collaboration is working well, it's a lot of fun to sort out obscure things like how newlines should be normalized, especially when web developers and users are affected by the lack of interop.
This is a lovely post. I'm quite often asked if people from different browsers argue with each other in CSS meetings. I usually say it's a lot more "huh... yeah that's not good ... how do we fix it?" That's especially true when it comes to the sort of situations described here.
My colleague @atbrakhi.bsky.social wrote a nice, cleverly titled post based on a very short exchange we had on Instagram the other day...
www.atbrakhi.dev/blog/browser...
I want Custom Attributes to exist - think Custom Elements (Web Components) but Attributes.
I've been working on a proposal, specs, and now a polyfill: www.keithcirkel.co.uk/custom-attri...
More coming soon!
Found a conventional use for atproto (replacing high school state associations/athletic conference/school sports websites) the other day and built a spec because I couldn't help myself.
it's live but I'll share a blog post about it before sharing
I'm worried about the web. I don't want to live in a world where most users of internet-connected devices consume their information and accomplish their tasks via a chatbot interface.
If you've ever tried using a new web API in TypeScript, you've probably hit this problem:
An API exists. It works in your browser. But TypeScript has no types for it.
The reason is a limitation that TS unfortunately applies to its built-in libs.
BUT, I've created a relatively simple fix 👇
#CSS `progress()` is now baseline! 🥳
I was trying to see if this could be used as a workaround for the lack of typed arithmetic (unit division) in Firefox, and it does work, sort of.
codepen.io/editor/maike...
(And yes I know there's already the `tan2(atan())` trick, but that has its own bugs.)
Major versions of Firefox now land every two weeks, so Firefox 155 dropped today with web platform features including:
🎉 Fully typed CSS attr()
🎉 CSS progress()
🎉 Promise.allKeyed() and allSettledKeyed()
🎉 Lots of new WebTransport stuff
…And more!
developer.mozilla.org/en-US/docs/M...
You should try out microsoftedge.github.io/Demos/pwa-in...! It feels like a huge step forward for web apps.
Kudos to @diekus.bsky.social, Lia Hiscock and others on the Microsoft Edge team driving this!
Explainer: github.com/MicrosoftEdg...