Philip Jägenstedt

Philip Jägenstedt

@foolip.org

Long live the web! Engineer on Google Chrome, ex-Opera.

403 followers345 following176 posts

Philip Jägenstedt reposted

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!

w3.org26 October 2026 | Open-World FedCM for Decentralized Social Networks | CalendarThe World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards.
Sam Goto@sgo.to

@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!

Philip Jägenstedt reposted

✍️ 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!

joshwcomeau.comThe Future of CSS ✨ • Josh W. ComeauEvery year, browser vendors collaborate via the Interop project to synchronize their efforts on new HTML/CSS/JS features. This year, there’s a ton of super exciting features being considered! In this ...

Philip Jägenstedt reposted

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.

Philip Jägenstedt reposted

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.

This post is unavailable.

Philip Jägenstedt reposted

I blogged about my picks for the Interop 2027 project: www.sarasoueidan.com/blog/interop... inspired by @vale.rocks @pawelgrzybek.com @tylersticka.com @ohhelloana.blog and others who have blogged about their rankings.

sarasoueidan.comMy top picks for Interop 2027— The personal website of Sara Soueidan, inclusive Web UI engineer
Sara Soueidan@sarasoueidan.com

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`.

Philip Jägenstedt reposted

My personal brain wants some things but my work brain wants others. So I was forced to blog about it: ohhelloana.blog/my-interop-2...

ohhelloana.blogMy Interop feature rankingI ranked my Interop 2027 choices for fun.
Firefox for Web Developers@webdevs.firefox.com

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

Philip Jägenstedt reposted

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.

Philip Jägenstedt reposted

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 😆

Philip Jägenstedt reposted

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.

Philip Jägenstedt reposted

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...

Philip Jägenstedt reposted

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@github.com

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/

Philip Jägenstedt reposted

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.

Philip Jägenstedt reposted

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

bryan newbold@bnewbold.net

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.

Philip Jägenstedt reposted

Oh this is nice! Can even bring back IE data if you really, really have to.

MDN Web Docs@developer.mozilla.org

🆕 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...

Philip Jägenstedt reposted

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.

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.

Philip Jägenstedt reposted

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.

Philip Jägenstedt reposted

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

Philip Jägenstedt reposted

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 👇

Philip Jägenstedt reposted

#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.)

codepen.ioCSS typed arithmetic using progress()A code demo by Maikel Krause created on CodePen
Firefox for Web Developers@webdevs.firefox.com

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...

Philip Jägenstedt reposted

This has been a long slog; getting the web-as-app-store use-case nailed has taken extraordinary care and years of iteration. Congrats to the team!

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...