Earlier quoted context omitted.
I hate what it does to my back button
HTMX is the solution
HTML Can Do That
211–220 of 249 posts
Re: HTML Can Do That
#212Related to this, I’d love that HTML natively support sortable tables. This is a common need but every single time I have to reimplement it.
You want client side table sorting? It's really easy to do this with server rendered HTML. Put a link with the sort param in the column headers and be done.
Re: HTML Can Do That
#213Related to this, I’d love that HTML natively support sortable tables. This is a common need but every single time I have to reimplement it.
That's what javascript is supposed to be for. All of this is what javascript is supposed to be for. HTML describes layout, CSS describes style, JS adds interactivity. Want sortable tables? Get a jquery plugin and spend five minutes, done. This was all solved a decade or more ago.
Re: HTML Can Do That
#214Hidden content was not hidden in Android Firefox.
Re: HTML Can Do That
#215The color input looks different depending on your browser and OS. https://master.dev/blog/the-color-input-the-color-picker/ Firefox uses the native OS color picker, which in Windows 11 still looks unchanged from Windows 95.
That's fine, everything doesn't have to look the same everywhere. It does matter when there's functionality a site relies on but it's not available in one out more browser/OS combinations.
Re: HTML Can Do That
#216also supports "srcset" which can make the image component responsive. Hope they add a placeholder to it which can account for loading state.
I find using with and is more flexible, particularly with multiple image formats (AVIF and JPG in my case).
Re: HTML Can Do That
#217The “hidden until found” feature surprised me. What’s the use case for something like that?
It won't be an intended use case, but it might be a convenient place to put poisoned content for the “benefit” of scrapers… Though humans will accidentally find it too, so using a details tag with appropriate summary as a warning would be more friendly than just hidden content. It'll still get opened, but the user at least has a way of closing it again afterwards. Also before using it I'd want to check what old UAs i…
Re: HTML Can Do That
#218Earlier quoted context omitted.
Once backend and frontend became two separate teams frontend people didn't want to keep asking backend to make logic changes for state, so frontend took things into their own hands. The mistake was making it two separate teams.
the frontend team can write a BFF to make all pages render server-side. there is an advocacy group for keeping oauth2 clients out of browsers which gives this idea some _political_ merit. in ways more than one, SPA is not the only solution when a dedicated _frontend team_ is employed.
Re: HTML Can Do That
#219Popover, dialog, invoker commands, our entire production app uses these everywhere and it works really well! The fact that dialogs and popovers are rendered on the "top layer" and that nested popovers are also automatically stacked on top of each other and have 'cascading close' shows how well these standards were designed. The only hard thing is still to position a popover near the element that triggers it, such as…
> LLMs are also terrible at these new standards. If they even know about them, they often think they're not baseline yet… It doesn’t have to be that way. You could create a Skill [1] that tells the agent to use modern css; the newer models like Opus 5 are probably much better with modern css. Google released a set of skills at I/O called Modern Web Guidance [2] that steer coding agents to use modern css and best prac…
Wrapping an .md file in all this circus, with lingo carefully designed to hide the fact that under the hood you're really just dumping another text file into the LLM's context , helps nobody but people's AI psychosis.
But I guess "my LLM can use skills" sounds a lot cooler than "my LLM can read text files", so we'd rather keep pretending really hard.
Re: HTML Can Do That
#220Earlier quoted context omitted.
> LLMs are also terrible at these new standards. If they even know about them, they often think they're not baseline yet… It doesn’t have to be that way. You could create a Skill [1] that tells the agent to use modern css; the newer models like Opus 5 are probably much better with modern css. Google released a set of skills at I/O called Modern Web Guidance [2] that steer coding agents to use modern css and best prac…
Can we stop calling them skills? They're mostly just documents like any other. Call them cheat-sheets or guides. Wrapping an .md file in all this circus, with lingo carefully designed to hide the fact that under the hood you're really just dumping another text file into the LLM's context , helps nobody but people's AI psychosis. But I guess "my LLM can use skills" sounds a lot cooler than "my LLM can read text files"…