Re:Using <details> for menus and dialogs (2019)
by montroser on Sunday April 25, 2021 @07:15AM
(#26931895)
It's a fair point that specs evolve, and that sometimes includes deprecation. I do feel slightly aggrieved about the `scoped` style attribute being spec'd, implemented, and then dropped shortly thereafter.
But overall I feel this approach has worked well over the years. With jQuery for example, I only learned enough to get by working in those codebases, but I committed to internalized all of the standardized DOM methods and Array methods and naive XHR workings. Now in these modern times, jQuery still _works_, but whatever I came to know of it is no longer very useful to me, day to day.
Re:Using <details> for menus and dialogs (2019)
by ryanbrunner on Sunday April 25, 2021 @07:15AM
(#26931893)
Deprecated HTML tags are relatively rare though, especially more recently. You can pretty much categorize every one of them into tags that are purely concerned with styling, frame support and applet type things. And in all cases, the deprecation took a long time, long enough that it would outlive most apps.
And nowadays, even if dialog happened to be deprecated, you could always continue to support it using a custom element if you really needed to (which probably wouldn't be the worst approach even if you were building it from scratch, to be honest).
Historically it's more likely that an unpopular tag will be removed from the HTML spec and removed from browsers than JS will lose compatibility with your code.
For example, a JS flashing text effect from 25 years ago still works. <blink> tags don't.
Most tags that are deprecated in the spec aren't removed (eg marquee) but you shouldn't assume something in the spec will be available forever.