The details / summary thing absolutely kills me. There’s basically nothing you can’t do with them. Hiding and replacing markers is easy. But every component library just pretends they don’t exist. It even saves you the effort of all the aria control and expanded tags: these tags don’t need them.
Replacing JavaScript with Just HTML
11–20 of 296 posts
Re: Replacing JavaScript with Just HTML
#12Writing a web server in C++ is a way to get excellent performance. So why don't most people do it?
Re: Replacing JavaScript with Just HTML
#13Re: Replacing JavaScript with Just HTML
#14Gimme a dark/light mode switch. CSS is allowed.
Re: Replacing JavaScript with Just HTML
#15Gimme a dark/light mode switch. CSS is allowed.
Re: Replacing JavaScript with Just HTML
#16When building out a new app or site, start with the simplest solution like the html-only autofilters first, then add complex behavior later. It's good to know these things exist so there are alternatives to reaching for a fat react component as the first step.
Then you're stuck with a bugfix's allotment of time to implement an accessible, correctly themed combo box that you should have reached for in the first place, just like what you had to do last week with the native date pickers.
Re: Replacing JavaScript with Just HTML
#17Re: Replacing JavaScript with Just HTML
#18The details / summary thing absolutely kills me. There’s basically nothing you can’t do with them. Hiding and replacing markers is easy. But every component library just pretends they don’t exist. It even saves you the effort of all the aria control and expanded tags: these tags don’t need them.
Details works even when it's set display:contents too, for even more flexibility. Can't animate from open›close, yet, though. That's pretty much my last frustration with it.