Live data from Hacker News

Cool HTML elements nobody uses

tapajyoti-bose.medium.com

31–40 of 111 posts

Re: Cool HTML elements nobody uses

#31
post #23
post #17

This and were so overused that browsers started to show them without any animation

Decades ago, I disabled blink by loading my netscape binary into emacs and changing the tag name. Surprisingly marquee is still there, you can even go into the DOM and rename your top level elements "marquee" and the entire page scrolls.

Re: Cool HTML elements nobody uses

#32

I didn't know about datalist, but now I'll start using it. I've been annoyed at the multitude of completion implementations that all behave slightly differently.

Yeah, it's really odd. Some browsers will only show the value, some will show the label and the value, and some will (properly) show the label when you have both a label and a value.

It kind of drives me nuts that it doesn't work the same way as the select element, when you are using option elements as a list.

Re: Cool HTML elements nobody uses

#34
post #18

I didn't know about datalist, but now I'll start using it. I've been annoyed at the multitude of completion implementations that all behave slightly differently.

i think the problem with datalist is the default styles, and the lack of customizability (eg if you want multiple slections, or to display descriptions or images next to each choice, or you want fuzzy matching). most of the time you'll just want to go ahead and import a ComboBox component someone else has made

The problem is more the inconsistent behavior. Styling is also a concern, but why doesn't the Option element behave the same in a datalist as in a select? (I think only Firefox actually does this properly).

Re: Cool HTML elements nobody uses

#36

Having used all of these in the past, here's why this is the case: 1. meter/progress - default style looks dated, styling works different on different browsers, the color scale options are confusing 2. sup/sub & 7. abbr - these are only useful for page content (as opposed to site design), which is usually WYSIWYG or something like Markdown. Many editors/parsers don't support it, at least by default. 4. map/area - it'…

For some reason makes me anxious. Is there some memory of the Flash/ActionScript days, or maybe ActiveX or something, that causes me to frown at seeing a mention of ?

Re: Cool HTML elements nobody uses

#37
post #4

> 4. map & area These take me back, but I'm trying to remember why I stopped using them. Did they go out of fashion? Or was it accessibility related?

I think they went out of style because they weren't javascript. But many older websites still use them to create fast loading, universally supported, interactive data visualizations that JS would still struggle to match. One of my favorites is the dynamic space weather visualization from Lockheed Martin Solar and Astrophysics Laboratory, https://www.lmsal.com/solarsoft/latest_events/

What's interactive about that example?

Re: Cool HTML elements nobody uses

#38
post #31
post #23

Earlier quoted context omitted.

This and were so overused that browsers started to show them without any animation

Decades ago, I disabled blink by loading my netscape binary into emacs and changing the tag name. Surprisingly marquee is still there, you can even go into the DOM and rename your top level elements "marquee" and the entire page scrolls.

Just did that to HN's . Got a good chuckle out of it, thanks.

Re: Cool HTML elements nobody uses

#39
SUB/SUP, MAP/AREA, and ABBR have all been in frequent use since the beginning.

MAP/AREA in particular was extensively used before table-based layouts. It was only once tables were added to HTML that individual images could be arranged into one large seamless-looking image while each piece was surrounded by its own anchor. Before that point, using MAP/AREA was a developer’s only option.

Re: Cool HTML elements nobody uses

#40

Having used all of these in the past, here's why this is the case: 1. meter/progress - default style looks dated, styling works different on different browsers, the color scale options are confusing 2. sup/sub & 7. abbr - these are only useful for page content (as opposed to site design), which is usually WYSIWYG or something like Markdown. Many editors/parsers don't support it, at least by default. 4. map/area - it'…

That was my first thought... if people don't use these very old elements any more, there's probably a good Chesterson's fence-type reason. Frames seemed really cool when I first saw them too, until I actually started trying to support them.
Post reply on HN