Skip to main content

Web Weekly #181

Guten Tag! Guten Tag! šŸ‘‹

Will you use Chrome's new <geolocation> HTML element? Are you excited about CSS anchor positioning going baseline? And do you know what a self-closing <div /> really does?

Turn on the Web Weekly tune and find some answers below. Enjoy!

Olivier listens to "Shelf Lives - Where Did I Go?" and says:

I simply love this song's power and energy!

Do you want to share your favorite song with the Web Weekly community? Hit reply; there are five more songs left in the queue.


The new Web Almanac was released! If you don't know about the project: the team behind it takes all the data gathered from the HTTP Archive to analyze and understand the "state of the web". It's always super interesting to read and, almost as a tradition, I went over it and shared the interesting facts on Bluesky. Here are some fun ones.

3rd party data stats are as wild as always. For all analyzed pages, the median 3rd party request count is around ~80.  80(!) third-party requests per page. 🤯

The amount of third-party activity on the web is just mind-boggling...

Not surprising and not new; only 48% of mobile comes with good Core Web Vitals.

The web is slow...

Nothing more to add. More is always better, right? 🫣  > As of July 2025, the same median page is now 2,362 KB

... and heavy. The median site is 2.3MB primarily to ship some text and images. Wild times!

If you're curious about more bite-sized stats, Geoff blogged about it, but either way:

Give the Almanac a read; it's a ton of work (kudos to all the authors and analysts) and you'll definitely learn something new!


A huge thank you and a huge bag of karma points go to Jens and Temani this week. Thank you for supporting indie publishing by covering a small fraction of the cost it takes to send Web Weekly every week! ā¤ļø

If you enjoy Web Weekly, too, join 34 supporters on Patreon or GitHub Sponsors. It really makes a difference!


If you enjoy Web Weekly, share it with your friends and family.

A quick "repost" really helps this indie newsletter out. Thank you! ā¤ļø


Something that made me smile this week

5 Awesome Scroll Fade Effects with Vanilla JavaScript: 1. Don't 2. Please don't 3. Don't it sucks 4. Seriously, don't do it 5. Bro please

David rants about the all-too-common "scroll-to-fade" technique. Thinking back, I've been lucky enough to never actually have to build one of these. I mean, why would you heavily delay showing precious content, right?

David's idea of the web developer community pretending that this feature is impossible to build made me smile, though.

We're all developers here. Can we collectively pretend scroll fade is technically impossible now?

Take care of scroll

It's funny though, because scroll-driven animations only recently entered the web. I guess it's like all fancy web dev things: let us all be responsible for the things we build.

No code

Exciting new Chrome features

Chrome is always at the forefront of releasing new things, but there have been some changes that really fix fundamental web issues. Bramus was on a roll and blogged about all of them.

From Chrome 145 onwards, 100vw will automatically subtract the size of the scrollbar from it if you have forced the html element to always show a vertical scrollbar or if you reserve space for it (using scrollbar-gutter: stable).

If you're fighting the problem that 100vw doesn't consider scrollbars, a Chrome change landing in 145 might help.

dialog { 	overscroll-behavior: contain; }  dialog::backdrop { 	overflow: hidden; 	overscroll-behavior: contain; }

You probably know the problem that when you open a modal dialog, you have to set overflow: hidden on the html element to prevent the underlying content from scrolling. It works but was never a good solution. Chrome now supports a better way to do it. Let's hope the other vendors follow suit quickly.

Vertical Tabs — Enables an option for showing tabs to the side. – Mac, Windows, Linux

And lastly, an experimental version of vertical tabs for Chrome is in the making. šŸŽ‰

Sound on websites

"Users will hate sound." -> Only if you do it poorly. Aggressive, loud, or unnecessary sounds are annoying; subtle, appropriate, optional sounds are not. The autoplay video backlash was about intrusion, not about sound itself. Context matters.

I know of exactly two websites that use sounds: one is Josh's blog and the other one is LinkedIn. Every time I upload a video on LinkedIn, it beeps, and honestly, I like it. Should there be more sound effects on the web?

Delight with sound

Bouncy window resizing

Window being resized. The text scales with the resize action and bounces back to a readable state.

Lynn Fischer redesigns her site every year, and it's always great. The 2021 redesign was incredible (resize the window!). This year the redesign is a bit more subtle but still includes fun resize functionality using the ResizeObserver API.

Bounce!

Web interface guidelines

Web Interface Guidelines — Interfaces succeed because of hundreds of choices. This is a living, non-exhaustive list of those decisions. Most guidelines are framework-agnostic, some specific to React/Next.js. Feedback is welcome.

I'm really no fan of Vercel, but their public interface guidelines include good stuff. Do you know of more companies putting these out? I'd love to learn about the UI quality standards of other big players.

Ship good stuff

The wonderful weird web – Draw on the world map

Artboard that includes "random" pixel art.

There's this site where people can log in to draw pixel art on the maps of this world, and it's a wonderfully weird collection of pixel art. This is how my area looks! šŸ‘†

Be fascinated

The custom elements manifest

The missing link for web components

I heard about the Custom Elements Manifest for the first time when Dave blogged about it, and it seems like it will improve the tooling around web components drastically.

If I understand this correctly, you can now scan, parse, and document your web components to display them in Storybook or have much-needed editor completions.

Document your web components

What actually is TTFB?

Why all the details? Well, to help you understand how useless it is to use 103 Early Hints just to get a better TTFB. Usually, the 103 response will contain useful stuff that helps improve performance. There are parties that just try to manipulate TTFB.

If you care about web performance, looking at Time to First Byte is often a first step. But what does this metric actually tell you? It turns out things are very complicated when you look at the first bytes. Robin provides massive detail and explains what you need to watch out for! Highly recommended.

And if learning about TTFB isn't enough, the post also includes some spiciness showing how "certain" companies fake a good TTFB metric with useless 103 Early Hints headers. Ouch.

Understand your metrics

More declarative HTML: <geolocation>

&lt;geolocation   onlocation=&quot;handleLocation(event)&quot;   autolocate   accuracymode=&quot;precise&quot;&gt; &lt;/geolocation&gt;

Chrome 144 (released last week) ships a new HTML element. And what can I say? I'm all for more native elements!

Ask for permission

And if you're into declarative HTML, you should definitely check out Invoker Commands, which recently went into Baseline!

For the Mac users

macOS Tidbits — Some neat conveniences for macOS users (or just the macOS-curious)

I thought I was pretty good on the Mac power user scale, but after reading these tidbits, I noticed that I need to level up. This tip, for example:

Hold ⌘ to interact with background windows without bringing them into focus.

I mean, what? How could I not know about this?

Be a power user

Random MDN – system-ui and friends

system-ui — Glyphs are taken from the default user interface font on a given platform. Because typographic traditions vary widely across the world, this generic is provided for typefaces that don't map cleanly into the other generics.

From the unlimited MDN knowledge archive...

Did you know that you can set the default operating system font via font-family: system-ui? There's also ui-serif, ui-sans-serif, ui-monospace, and ui-rounded; they're Safari-only, but useful if you're after the original Apple look.

Match the system

TIL recap – Are self-closing HTML elements a thing?

&lt;div class=&quot;blue&quot; /&gt;   Blue   &lt;div class=&quot;red&quot; /&gt;     Red     &lt;div class=&quot;green&quot; /&gt;       Green     &lt;/div&gt;   &lt;/div&gt; &lt;/div&gt;

Trick question: can you imagine what the HTML above renders? Note the self-closing div elements.

I won't reveal the answer, but there's a high chance that you'll be very surprised.

Understand HTML

Find more short web development learnings in my "Today I learned" section.

New on the baseline

Multiple boxes explaining the concept of anchor positioning. There's one box in the middle and multiple boxes are anchored around it.

With Firefox 147 (released last week), CSS anchor positioning moved into cross-browser territory. If you were holding back on learning this incredible new CSS feature because the browser support wasn't there, now's the time to look into it!

And a good start is the CSS-Tricks reference guide.

Anchor

And if this guide is too long for you today, here's a very practical example from Chris.

Three valuable projects to have a look at

A new Tiny Helper

ReliCSS with a textarea on the left and recommendations to remove old CSS on the right.

Do you remember all those wild CSS hacks we had to deal with a decade ago like *+html .ie7-only {} or ::-moz-selection? Luckily those times are mostly gone, but they'll probably live on forever in old CSS resets andaAbandoned sites. If you want to double-check whether you're shipping relics from the past, ReliCSS can help discover them.

Forget the past

Find more single-purpose online tools on tiny-helpers.dev.

Thought of the week

Here's Jim (one of my favorite bloggers) with something I can very much stand behind in the new world of "no effort" creations and coding.

My desire to give you constructive feedback is in direct correlation to your effort to care — about your communications, about what you ship, even about what you don't ship.

Did you learn something from this issue?

ā¤ļø If so, join 34 other Web Weekly supporters and give back with a small monthly donation on Patreon or GitHub Sponsors.

This is all, friends!

Loved this email? Hated this email? I want to hear about it!

If you think something needs improvement or something sparked some joy, reply to this email because I want to know more!


And with that, take care of yourself - mentally, physically, and emotionally.

I'll see you next week! šŸ‘‹