Quick reminder, if you're working on a SaaS product that requires a login, please check if you've defined the well-known URL to change passwords. Password managers will check `/.well-known/change-password` to offer a quick way to change passwords.
Stefan Judis
Sharing web dev tricks with 6k people at webweekly.email
Today I learned Blogger
Maintaining tiny-helpers.dev
Pronouns: he/him
`autocorrect` is Baseline Newly available! It accepts "on", "off", and "" (same as "on"). Browsers default to "on", so it's mostly a matter of turning it off. Doesn't apply to URL, email, and password inputs.
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/autocorrect
Have you seen all these new HTML elements entering the platform? There's ``, ``, and ``, just to name a few. Granted, many of these are Chromium-only, but I like where we're heading.
https://blog.master.dev/new-things-you-should-know-about-html-here-in-mid-2026/
A new Git version just dropped and it comes with a new experimental `history` command!
`reword` can be used to change commit messages and `split` can untangle a single commit into multiple ones.
No more interactive rebase. 🎉
https://github.blog/open-source/git/highlights-from-git-2-54/
The CSS working group came up with a new way to select prefixed classes. The Class Prefix Selector `.btn-*` matches `btn-primary`, `btn-secondary`, and whatever `btn-` class comes next.
I'd say I was pretty aware of all the possibilities and information my browser shares about me, but it's still wild to see all this data in black and white. :/
This is absolutely beautiful and very well done.
> Nothing you own is finished. Everything exists in a state of permanent incompletion, permanently needing.
I'm pretty sure I read this post years ago (seems to have been extended since) and I'm still following some of these rules. Perfect stuff for people that don't have an eye for design... 😅
If you're dealing with AI slop replies, you might appreciate these links. 👇
https://www.rickmanelius.com/p/aidr-ai-didnt-read
https://dontpastetheai.com/
Interop for 2026 is in full swing. Chromium is leading and has almost finished all its 2026 promises. We're in September, so that's cool. Firefox and Safari aren't that far behind.
We can now all submit focus areas for next year.
And the new Web Weekly is about to hit all the inboxes. 🫣
This time, it includes Interop 2027 focus areas, lots of new HTML elements, an explanation of ESM resolution, and the `progress()` CSS function going Baseline.
Enjoy!
Here's Jake sharing yet another detail about custom properties that I'm sure not many people know about. It's funny how many footguns can show up in a "simple variable system".
Jake's article is great. I'm sure you'll learn something!
https://jakearchibald.com/2026/css-custom-property-compute-time/
There's nothing to see here, it's just a browser running in your browser. 😅
With Firefox 155, released September 1st, the `progress()` CSS function became Baseline newly available. 🎉
https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Values/progress
HTML reminder: if you're dealing with elements that shouldn't be accessible or reachable at all, the `inert` attribute helps out!
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/inert
Do you know that you can use `image-set` to serve different background images right in CSS? Now you do and `image-set` is "widely available" since last month! 🎉
https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Values/image/image-set
Here's a little CSS-only trick to store the info of whether an element was previously focused. 👏
Have you ever noticed that "things become unclickable" when a view transition is running? You can work around this behavior with some CSS or scoped view transitions... 👇
https://master.dev/blog/view-transitions-careful-not-to-make-stuff-unclickable/
I really like this comparison. Daniel put CSS states (`:focus-visible`, `:popover-open`, `:fullscreen` etc) next to possible JavaScript implementations. He also went into the fairly new `event-trigger` CSS props and that's some fancy stuff!
Firefox will start supporting `ariaNotify` in release 150.
If you haven't heard of it, `ariaNotify` allows you to provide text that should be announced by a screen reader if available and activated. No more fiddling with live regions. 💪
According to MDN, Chromium shipped the method in an "unreliable" state. Let's see how the Firefox version behaves.
MDN: https://developer.mozilla.org/en-US/docs/Web/API/Document/ariaNotify
Ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=2018095
Responsive images are tough and often implemented incorrectly. With sizes=auto the browser will figure things out.
Chromium supports it, Firefox 150 in two weeks, Webkit in tech preview. I can't wait for this!
TIL recap: `field-sizing` enables textareas to automatically grow. And that's great, but do you know that it works for "normal" inputs and `select` boxes, too?
https://www.stefanjudis.com/today-i-learned/field-sizing-is-about-more-than-textareas/
If you're intimidated by the Chrome DevTools performance tools, you'll like this one. It's a nice explainer about all the details you need to know!
I must admit this was harder than I thought. 😅 CSS or BS?
Lazy-loaded video/auto elements are finally coming to the web! 🎉
Here's Temani yet again doing Temani things explaining how to tweak and adjust the overflow of individual images using `object-fit` and `object-position`. It's a great read to understand `img` fundamentals.
https://master.dev/blog/something-nobody-told-you-about-the-image-element-it-can-overflow/
I remember when MDN got a little style overhaul last year, but I didn't realize that it was an entire rebuild to drop React.
"Our React app was merely a wrapper around our static content."
The new MDN is built with a custom render pipeline and Lit web components. The article is a great deep dive!
https://developer.mozilla.org/en-US/blog/mdn-front-end-deep-dive/
I dig this a lot! Edge now ships an experimental feature that warns you about and monitors network activity that isn't optimized, like uncompressed assets or large images.
https://www.debugbear.com/blog/network-efficiency-guardrails
It's always astonishing how many "I've been doing this since forever..." replies you get when you share something you learned and it gets some reach. Absolutely wild.
Josh published a new post, and we all know what this means: lots of demos and eye candy. I'd forgotten about the ability to overwrite the SVG `d` attribute in CSS. Still on the fence about whether that's a good idea. 😅
Web Weekly 190 just went out! 🥂
This one covers `image-set` for backgrounds, Wakamai Fondue v1.0, `field-sizing` for textareas, selects and input fields, CSS quirks in the shadow DOM, and container style queries in Firefox Nightly.
Read it online: https://webweekly.email/archive/web-weekly-190
New on the blog: TIL about TypeScript assertion functions (`asserts data is Something`). Usually I use type guards but with assertion functions you can apply a type to the current scope. Good stuff!
https://www.stefanjudis.com/today-i-learned/the-scope-of-type-guards-and-assertion-functions/
If you sometimes see Times New Roman flashing, Harry describes that the issue is most likely incorrect font-family properties. I bet many people have these issues in their stylesheets. I should probably check mine too.
https://csswizardry.com/2026/04/font-family-doesnt-fall-back-the-way-you-think/
Man, I love this. Here's a custom element to automatically add side notes to your blog posts. It parses the text, includes feature detection for anchor positioning, and uses progressive enhancement.
This is how things should be done!
https://meyerweb.com/eric/thoughts/2025/10/29/custom-asidenotes/
Happy Monday, friends! 🥳
A new edition of my Web Weekly newsletter lands tonight.
It'll include the usual mix of web dev discoveries, spec updates, browser news, and things that nerd-sniped me last week.
Subscribe and join the fun! 👋
The yearly WebAIM report is out and the overall accessibility state of the web is getting worse again.
"Home pages with ARIA present had significantly more errors (59.1 on average) than pages without ARIA (42 on average)"
Man, this makes me sad.
@joshix@fosspri.de How so? And have you read the section about preload in the linked article?




