While we took a decade to decide on a few tags on the HTML namespace, CSS snuck in several hundred into a single namespace. 
-
-
I do think <input> could have been a better experience, but that goes back pretty far :)
-
I'm only talking about usage, not whether it is good. Do people use <progress> now or divs with jquery? I see mostly divs in sites I look at
-
Not sure what you're saying here really -there are a lot of challenges to use. People do want good/simple answers, we're not great at giving
-
People create their own spinoffs of native elements not because they'd rather do something harder, right?
-
I'm just (possibly incorrectly) observing that many elements aren't widely used. I don't have an opinion as to why.
-
I don't disagree many aren't used as widely as people hoped but I attribute that likely to mismatch/how they were created not lack of want
-
I could also be wrong, but I feel pretty strongly there's some 'there' there.
-
I also don't think this is accurate. Usage is not evenly distributed but it's not uncommon.
End of conversation
New conversation -
-
-
In terms of usage? Probably just the media ones. nav and header pretty successful.
-
But if you go to a website that has an address, what are the chances it is using <address> I think slim! How many modals are <dialog>?
-
If someone has to implement modals and focus management, <dialog> is the one true saving grace that has blessed us all.
-
I'm reading this tweet in a modal on https://twitter.com , it doesn't use dialog:pic.twitter.com/jMvl0gHUIg
-
having done focus management/used a screen reading/using `tab` key ... twitter web ui isn't the best thing ever.
-
screen reader is verbose / doesn't give guidance, can't tab to exit on top right, can't tab out of page to the url bar :(
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.