Yes I literally worked on a PWA with this exact feature.

I believe you can see it working on TikTok web as well.

You just can’t have the first video unmuted on initial load, although I wonder if this can be relaxed when user installs a PWA.

I drive like this too, but I think we’re a small minority. Especially here in LA.

Haha I did the same with our product manager and designers. One of our designers just got her first (tiny) PR merged this week.

I am somewhat fearful of having created a monster, but at the same time I think it’s good to knock down barriers to knowledge and learning. All else equal, I think a designer or PM with some exposure to code is better than one without.

What I’m fearful of are 10k line PRs and pressure from product to “just ship it.” Past a certain threshold a PR will be really tough to review, to the point that it would be preferable for an engineer to have handled it from the start.

I think we will need deeper integration between figma and the codebase/storybook. Shared color palette definitions, integration of storybook components with figma components, stuff like that.

The Figma MCP that you can use to handover to your agent and simply say “implement this” is already pretty impressive.

Is it clear though? It looks like an icon for a drawing app, not a word processor.

I run a 42” 4k at 1:1 pixel ratio and I agree. It’s a little too big, but it does nice double duty for gaming and watching tv.

5120x3200 in 30” would be awesome.

Dan Abramov just posted about this happening to him: https://bsky.app/profile/danabra.mov/post/3mca3aoxeks2i

I've been working on a polyfill for the new Navigation API: https://github.com/kcrwfrd/navigation-ponyfill

I've been super hyped about it. My main goal at first was supporting `navigation.canGoBack` and the `currententrychange` event simply so that I could implement perfect back buttons with (almost) zero edge cases. This is surprisingly very tricky with the older History API.

Today I just opened a PR with support for `entries()` and `currentEntry`: https://github.com/kcrwfrd/navigation-ponyfill/pull/33

Once that lands I'll be able to start thinking about implementing full-blown navigations with it, with cool stuff like navigation interceptors and whatnot. That would actually enable framework router implementations wholly based off the Navigation API, rather than simply patching some enhanced capabilities for use with a router based on history.pushState / history.replaceState.

I find this fun and whimsical, but surely it’s an accessibility nightmare.

No difference from using a div/span.

simply only ever use this to replace <span> or <div>

aria tags for days

Yes, the hydration behavior of custom elements is nice. You don’t even need to do anything special with JS bundle loading.

Simply render your <element> (server-side is fine) and whenever the JavaScript downloads and executes your custom elements will mount and do their thing.

I love the transaction history in YNAB. I refer to it all the time.