Jon Lunman
jlunman.bsky.social
Jon Lunman
@jlunman.bsky.social
Software Architect. Web standards nerd. Front-of-the-front-end enthusiast. RESTafarian. Occasional musician.

https://soundcloud.com/jon-lunman
I'm honestly amazed they haven't done this yet.
December 7, 2025 at 12:37 AM
Ooh that's a great use!
December 2, 2025 at 5:48 PM
I like it. Is this actually being worked on (or at least considered) by any browser teams, to your knowlege?
November 26, 2025 at 7:52 PM
Thank you! (and @miriam.codes!)

I learned something new today, and that's always fun. 🙂
November 21, 2025 at 10:08 PM
Basically trying to give users multiple paths to the same options, to avoid them having to scroll all the way up to the top of the page.
November 21, 2025 at 9:17 PM
I'm mainly exploring options for a progressively-enhanced context menu, where the same menu could be invoked either from the top of the page, or from a button on the selected items.
November 21, 2025 at 9:15 PM
Reposted by Jon Lunman
Just saw an extended version
November 20, 2025 at 11:26 PM
Also iframes that can automatically size to their content.
November 6, 2025 at 2:43 PM
Would also love to be able to conditionally disable elements with CSS. Similar to "pointer-events: none" but also covering keyboard and other interactions.

Combined with my previous request for a ":navigating" pseudo-class, this could be used as to prevent double form submissions:
November 6, 2025 at 1:54 PM
I would love a way in CSS to detect when a navigation has been triggered by a link, form, or button that submits a form.

This would allow us to provide better visual feedback that a navigation is underway. Especially useful if the network is slow.

Hypothetical examples:
November 6, 2025 at 1:44 PM
A list of users that just happens to be sorted alphabetically can be a <ul> (unordered list), because the nature of those users isn't affected by what order they're presented in - there's no special meaning to the order itself.
October 30, 2025 at 4:26 PM
I know this was a shitpost, but for the sake of anyone who genuninely isn't sure: <ol> should be used for lists where the order itself conveys meaning, and implies a relationship from one item to the next. e.g. links in a breadcrumb or steps in recipe.
October 30, 2025 at 4:26 PM
Reposted by Jon Lunman
Correction: I'm told that the SvelteKit benchmark does actually perform the same work as next.js. The "vanilla" benchmark, though, generates like 3x the HTML.
October 15, 2025 at 12:17 AM
A note of caution, however. This particular syntax will select not only the parent, but all of its ancestors as well.

Use :has(>&) to select only the direct parent.
September 24, 2025 at 12:39 PM