71–80 of 111 posts
SUP and SUB I find don't work very well with glyphs, but work fine with standard Latin characters.
My favorite obscure useful HTML elements: , , , / / , / / / .
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.
Earlier quoted context omitted.
This and were so overused that browsers started to show them without any animation
A couple years ago I went looking for JS marquee replacements and zero of them I could find would deliver the same functionality as Functionality's gone, it seems. Evidently it's hard to replicate all of it because none of the options I could find managed it.
Earlier quoted context omitted.
A couple years ago I went looking for JS marquee replacements and zero of them I could find would deliver the same functionality as Functionality's gone, it seems. Evidently it's hard to replicate all of it because none of the options I could find managed it.
You don't need javascript to replace marquee tags. There are a plethora of implementations using CSS animation.
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/ma...
I just know that when I went to try to make a marquee using some of these features a couple years ago, I couldn't find anything pre-made that could do what I wanted, which was nothing more than what could do, so it was going to be a lot of custom work. Which surprised me, I expected someone to have perfectly re-created the whole tag just for giggles if nothing else. There were tons of partial solutions, but nothing that was a complete replacement.
Earlier quoted context omitted.
That was largely iframes, though they are still in use for some things like certain methods of ad delivery. frames/framesets were often about partial updates, but mostly where script wasn't wanted so AJAX (once available) wasn't an option either.
Having lived through that era, Frames (and Framesets) were mostly killed by the proliferation of PHP on cheap hosts. A lot of Frames were used for building navigation elements without a lot of copy/pasting between HTML files (headers, footers, navigation bars, etc). The alternative to frames was either copy/pasting or ancient early static site generators. When PHP became common and cheap most people moved to server-s…
also, CSS Flex
and has the problem that they change the line height. So if you have an paragraph and one line contains "Nice ground with 42 m² grass" then that line is taller than all the other lines, which makes it rather ugly. So I automatically converts all m 2 and similar into the unicode symbols: https://en.wikipedia.org/wiki/Unicode_subscripts_and_supersc...
The W3C recommends to prefer the markup versions, and various years the Unicode committee has also suggested not to use the Unicode versions except in backwards compatibility with old ISO codes and in certain semantically more meaningful situations as "single words" (chemistry formulas more so than math, for instance). Though the Unicode recommendations have waffled back and forth over the years. Both have recommended it in part because of metadata available to screen-readers for accessibility.
Not that you always have to follow such recommendations from groups such as these, just that it is useful to know what the recommendations are. Also as others pointed out, some CSS stylesheets are better than others at line-height of sub/sup markup and while the default styles are kind of awful, it is useful to know there are CSS options.
https://en.wikipedia.org/wiki/Unicode_subscripts_and_supersc...
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'…
Browser defaults for all HTML elements look "dated". The visual appearance of meter, as with all elements, is adjusted via CSS.
> . map/area - it's absolute positioning, which is unusable for the variety of devices we use today
It's relative to the image dimensions, not the page/viewport.