Less “best kept secret” more “not very useful so nobody cared to learn about it”.
Nearly every web app that uses an
inputcalculates and displays some result based on those inputs. It’s clearly useful.You can do that with a div. Its only use is slightly improved default accessibility behaviour.
Yes exactly. Which is reason enough to use it, unless you purposefully want worse accessibility.
You could make the same argument about
p,h1-h6,label, etc.All those other elements give some benefit apart from accessibility which is why they are universally used and
outputisn’t.Expecting all devs to test their sites with screen readers is unrealistic.
Expecting all devs to test their sites with screen readers is unrealistic.
I disagree with this but its not what we’re talking about. You said
outputis useless and I’m saying its obviously not. There’s zero cost to using it instead of a div so the only reason not to use it is to purposefully screw users who need accessibility features.All those other elements give some benefit apart from accessibility
Maybe for
labelbutpandh1-h6only differ fromdivin styles, which is another argument in my favor. If you’re willing to swap adivfor one of those for visual users, swapping adivforoutputshould be just as easy of a change.You said output is useless
No I said it’s not very useful.
There’s zero cost to using it instead of a div so the only reason not to use it is to purposefully screw users who need accessibility features.
No, the main reason is because people don’t know about it, because it’s an extra thing to remember for little benefit. Same reason other semantic-only tags like
articleget very little use.only differ from div in styles
Err yeah the “only” do a really useful thing that lots of people want.
If
outputcame with some nice styling and maybe animations… maybe a built in copy-to-clipboard option… then people would have used it.the main reason is because people don’t know about it
But you know about it now and you’re still arguing against it.
it’s an extra thing to remember for little benefit the “only” do a really useful thing that lots of people want.
The benefit you see in those tags is the same level of benefit that users who use accessibility features get from
outputand other semantic tags. But your argument seems to boil down to “I dont need accessibility features so i don’t care about enabling them for ppl who do”. That’s very disappointing and continuing this debate seems pointless so i’m gonna stop here
htmls best kept secret; the marquee tag
I’ve been writing HTML since like '98 and am just learning about this tag now.
If you prefer reading instead of watching:
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/outputWhat do you mean by “instead of watching”? OP links to a text article.
I still prefer your MDN link though. Concise, and a more readable layout. Dunno why OP felt the need to increase the font size that much into a wide layout.
I have no idea why I thought it was a video.
