Scott Jehl

How to Use Responsive HTML Video (...and Audio!) | Scott Jehl, Web Designer/Developer Now that responsive HTML video delivery works across all browsers, let's look at how to use it

Here’s how scottjehl.com/posts/using-...

Found a popular website serving “responsive” videos via 2 <video> elements that are shown or hidden via CSS breakpoint. Don’t do it that way, friends! Too costly!

You can set media attributes on video sources now and only download the source a browser needs; even to deliver portrait vs landscape.

Me, sitting behind a cuddly toy of a fox. Ok it's obviously Firefox.

Starting my new role on Monday. Could be anywhere.

forgot that too

A picture of the pedestrian pathway leading up to the Brooklyn Bridge, taken from the Brooklyn side of the East river.

I have a morning checklist for packing everything for my run commute into Manhattan (towel, work clothes, laptop, etc). And yet, I forgot my belt again today.

Did you know a running shoelace can be a belt?

Responsive video is (almost) easy now | Koos Looijesteijn How to serve high-quality, vertical and horizontal video variants and break free from platforms like YouTube

Nice post from @kooslooijesteijn.net

webdev thought: I was noticing last night while working on a service worker, the network-first pattern that @adactio.com long wrote about for HTML requests works pretty nicely for JS and CSS files that change a lot too. Worker looks to network first (which may hit regular browser cache) 👍

Google's AI recommends css overflow: normal as an equivalent to overflow visible

it didn't look familiar to me so I searched "is overflow: normal" a valid value? its AI says, no it's not. Just made it up!

ah yes, overflow: normal

For a while I might've said, "most websites should work before JS loads, but if you're building Slack then do whatever works." But my perspective on that has evolved too. I think the Slacks would clearly benefit from a PE ethic now too. Do we need JS routing? Can this react menu can be a <select>?

To give an example, if I'm auditing a site that generates or reveals some or all of its HTML content with client-side JS, I'll see its user experience vary wildly based on users' devices. And there's typically no easy fix to offer. Someone chose an architecture that forfeited access to fast delivery

Thx for the context. That's an example of a pattern that uses Progressive Enhancement, no doubt. But I do kindly disagree: PE (the pattern delivering pages that are already-useful/renderable before enhancing their behavior/statefulness with CSS/JS) is as critical in my work today as it ever has been

So, I disagree. The most consequential rendering performance and site reliability bottlenecks I see day-to-day are from over-reliance on client-side JS. And they're often the hardest to fix, since the problems stem from big/early architectural decisions about the need for delivering useful HTML

Framing PE as a practice specifically for supporting folks who disable JavaScript has always been a disservice to the greater benefits of the patterns. Reducing reliance on client-side JS for handling tasks (eg HTML generation) that are better handled by HTML and CSS is as helpful today as ever.

Billionaires Convince Themselves AI Chatbots Are Close to Making New Scientific Discoveries

painful context gizmodo.com/billionaires...

way too online already today

einstein couldn't tie his shoes so that kalanick couldn't log into grok 4 girlfriendbot

great!

ah, gotcha. Do the demos at the bottom of that post work expectedly for you at least? (Note that "expected" only applies to initial page load, as sadly any further responsiveness isn't supported anywhere (yet?).

Yesterday marked my first whole year of helping make all those websites that run on Squarespace more performant, resilient, and accessible. That went by fast! Good place, good team, big challenges. 🖤

seems to do the trick. What are you seeing?

Yeah? Hmm. The demos seem to do what they’re supposed to on my iOS safari.

Ah! huh yeah that makes a lot of sense

Nice. For my course I used a similar pattern with connectedCallback containing a mutation observer that calls init() as soon as the custom element’s childnodes exist, which protects against those scenarios where CC will fire as soon as the opening tag is encountered. I can try and find it…

every rental car desk has the vibe of an outpost that HQ has long understood to have been closed

An HTML Templating Language That Keeps Its Secrets | Scott Jehl, Web Designer/Developer I think it would be nice to have a templating language whose output can still be input

Could it be done in a sort of microformat/attribute syntax so output can be reused as input? scottjehl.com/posts/declar...

Agreed

Glad to see it

👏

Hire Nathan!

That’s awful, Nathan. So sorry to hear that. Massive loss for them.