Grrr… it turns out that browsers exhibit some very frustrating behaviour when it comes to the video element. Rob has the details…
I wasn’t able to tune into this live (“tune in?” what century is this?) but I’ve enjoyed catching up with the great talks like:
Bruce raises an interesting question with media playing in popovers—shouldn’t the media pause when the popover is closed? I agree with Bruce that this is a common use case that should be covered declaratively.
A great talk from Addy on just how damaging client-side JavaScript can be to the user experience …and what you can do about it.
The capture attribute is pretty nifty—and I just love that you get so much power in a declarative way:
<input type="file" accept="image/*" capture="environment">
This is a terrific and nuanced talk that packs a lot into less than twenty minutes.
I heartily concur with Rich’s assessment that most websites aren’t apps or documents but something in between. It’s a continuum. And I really like Rich’s proposed approach: transitional web apps.
(The secret sauce in transitional web apps is progressive enhancement.)
Measuring performance is important. Communicating the story of performance is equally important.
Diagnosing a video playback issue in Safari, thanks to a timely blog post.
Some handy tips courtesy of Chris Ferdinandi.
Naming custom elements, naming attributes, the single responsibility principle, and communicating across components.
HTML web components for augmenting date inputs.