Can you tell CSS from BS? I tried, and it's hard.
| GitHub | https://github.com/jakearchibald |
| GitHub | https://github.com/jakearchibald |
Can you tell CSS from BS? I tried, and it's hard.
Folks asked if there was a way to disable Chrome's own 'back' transitions, and I didn't think there was, but… you can use a CloseWatcher to listen for the back gesture (which disables Chrome's transition), and then call history.back().
Because you can provide arbitrary image data to the encoder for the progressive passes, you're in full control over what those passes look like.
In this example, I've created a pass that's blurred except for the 'focal point' of the image (I'm not sure it's a good effect though).
Live demo: https://random-stuff.jakearchibald.com/apps/partial-img-decode/?demo=cat-3-pass.avif&density=2, although the progressive rendering is Chrome-only right now.
Firefox bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1712813
The progressive passes work like frames of a video, in that subsequent passes can be inter-frames, reusing data.
There's something quite exciting happening with AVIF and progressive rendering.
Some recent patches let you provide custom 'frames' as progressive passes, so you can provide e.g. smaller blurry versions of the full image to use as a progressive pass.
I've proposed a series of changes to popover=hint. If you use web popovers, I'd love to know if the changes in the first post of this issue make sense, or, more importantly, if these changes would break your current usage of popovers.
https://github.com/whatwg/html/issues/12304#issue-4121948352
@jaffathecake has been producing short-form video on web platform stuff recently, and the videos are assembled, edited, and encoding entirely in the browser. In his session at All Day Hey! 2026, he'll dive into the new shiny features that make this possible.
Schedule and tickets: https://heypresents.com/conferences/2026/schedule