|
5 posts total
I'm excited that we're finally getting a customisable <select> on the web. However, there's one detail of it I'm really not sure about, and I'd like to hear your thoughts. Have your say before it's too late š https://jakearchibald.com/2024/how-should-selectedoption-work/ `el.className` and `el.htmlFor` have such unusual names because `class` and `for` used to be reserved words in JS. That hasn't been true for property names for 10+ years. Firefox is experimenting with adding `el.class` and `el.for`, yay! https://github.com/whatwg/html/issues/9379#issuecomment-2357214793  @jaffathecake this year has been a succession of discoveries of stuff which I have believed is true for years (sometimes decades) and I have never revisited. Radix parameter to parseInt()? Not required. NodeLists don't have .forEach? Yes they do. Property names are allowed to be reserved words? This is the latest surprise. Next someone will tell me that with{} is OK or something Since it's Christmas: CARROT IN A BOX https://youtu.be/emidnnQi-bg?si=zWPieFo5TlQE92DH (Sorry for the Jimmy Carr link, the other copy of the video is region locked)  @jaffathecake that and the joe wilkinson potato throw saga on taskmaster are easily the two best moments in television history You probably shouldn't ever ship view transitions like this, but eh I had fun. Demo: https://simple-set-demos.glitch.me/gross-cube-transition-shaded/
Show previous comments
@jaffathecake next do the "genie" thing from old versions of the osx dock where a page goes down into an icon. Could be a whole new field of mid-2000s visual transition effects š  @jaffathecake this is legit pretty cool for slide decks. HTML presentation stuff I've seen is usually a single giant file with a bunch of JS, but native HTML and CSS where each slide is a distinct document? Iām down.  I wonder if browsers could support VSCode-style wrapping for preformatted content https://github.com/w3c/csswg-drafts/issues/8733 @jaffathecake This would be great to have! A quick experiment of mine two months ago: https://fosstodon.org/@rauschma/109859060700688473 |
Gregory's Server
@jaffathecake Is <option> continue to be text only? If so, it should be easy to duplicate the text in <selectedoption>.
Speak from my brief experience as an implementer, anything resembling <svg:use> opens a rather big can of worms.
@jaffathecake I would vote for doing nothing by default, and having the other scenarios solved with js. If you need it to do something advanced then bring a bit of javascript code to do that. It's much better than having to do something weird or performance problematic by default with only a complicated way to prevent it.
Thanks to everyone who gave feedback on this. The group resolved on going with the first option in this post: Clone once when the selected option switches, and that's it.