Ryan Townsend
@twnsnd.com
680 followers 200 following 190 posts
Technology Leader & Distinguished Software Engineer • 20+ YOE in Tech, 10+ as CTO • Public Speaker • LessonsofaCTO.com & TWNSND.com
Posts Media Videos Starter Packs
Has this been discussed with Webkit/Apple? I know they had reservations about prerender, but maybe this is a more palatable middle ground?
I like it's cute little butt, but that's about it.
Northern UK developers: join us tonight in Manchester for a talk on scaling to support hundreds of millions in client transaction volume.

It contains a lot of framework-agnostic advice, so non-Ruby developers stand to learn a thing or two too!
Zurich, St Gallen then took the train down to Grindelwald (near Interlaken).

Definitely also going back one day.
Exactly the response I had when I went last year, “holy shit, the photos don’t lie!” Unreal.
Is this mob programming?
For the second part: I do think a pseudo-element for the min/max constrained area of the first/last slider-segment would be useful, so you could style that differently (for example adding cross-hatching, maybe a right/left border to indicate the stopping point)
The use-case I was thinking about is dynamically changing the number of ranges within the group and avoiding having to restyle, but actually with a fresh mind (and coffee), it's clear `nth-child`/`nth-last-child` solves that anyway – so ignore the first half of my reply.
Admittedly, I didn’t go that deep on the implementation.

Looking now, it’s hard to visualise on my mobile but is it guaranteed the injected scripts won’t also execute synchronously when browser-cached?
I guess with continuation you get the `triggerScripts` sooner if there’s no other work.

If I have my logic correct, double rAF lets newly-queued events/timers occur before `triggerScripts`.
Depends when you want the code to run, I guess. Generally writing to the DOM should be within a rAF to minimise the chance of layout thrashing.

Plus rAF works across all browsers.
It won't let me edit my response, but one further thing I'd like to add would be `::slider-segment` state, e.g. `before`, `after`, `between` (rather than solely relying on `nth-child`) and—most importantly, imo—`capped` for styling areas of the slider which are 'constrained' by min/max.
Reposted by Ryan Townsend
Bramus @bram.us · 14d
At #fronteers #DarkMode, @utilitybend.com proposed the HTML Element.

It unlocks the multi-handle range slider, a pattern you might have already seen when picking a price-range.

Feedback Form (with links to the explainer and demos): docs.google.com/forms/u/0/d/...
B, but with two constraints:

1. each release should be useful independently (e.g. it might cover just one use-case within the wider scope)
2. support for each release should be independently detectable (via `@supports` and the usual JS mechanisms)
Fwiw @jensimmons.bsky.social I'm totally with you that there could be better names out there.

I use both APIs daily and I still have to look up whether it's 'Command Invokers' or 'Invoker Commands' 🤷‍♂️
💯 came to say the same things @utilitybend.com

Also don't Interest Invokers act differently on mobile? (or at least it's being discussed? e.g. tap instead of hover)
Reposted by Ryan Townsend
messenger.abeto.co

This is freaking insane. The level of polish necessary for this visual fidelity and it all runs flawlessly on mobile. Hats off.
Messenger
It's a small planet, but someone's gotta make the deliveries.
messenger.abeto.co
When you can hear a picture