The right tag for the job: why you should use semantic HTML

Re:The right tag for the job: why you should use semantic HTML by Swizec on Sunday June 06, 2021 @04:54PM (#27416232)

Based on my experience as a web developer working with many designers over some 20 years of design trends, here’s the problem:

Default styles aren’t pretty.

That’s it. They’re superior in every other way. You always know what to click, you always know what an element will do, how it behaves, the UX is consistent with your OS, etc. Default elements are fantastic.

[ Parent | on HN ]

Re:The right tag for the job: why you should use semantic HTML by felixfbecker on Sunday June 06, 2021 @07:11PM (#27417228)

> the UX is consistent with your OS

Buttons in Chrome on macOS look completely different than in native apps. Buttons and context menu in Chrome's native <video> controls look yet again different, following Material Design. From the things one could argue are good about native browser styles "consistency with the OS" is definitely not one of them.

[ Parent | on HN ]

Re:The right tag for the job: why you should use semantic HTML by markdown on Sunday June 06, 2021 @09:43PM (#27418113)

Not datepickers. The datepicker element is garbage.

[ Parent | on HN ]

Re:The right tag for the job: why you should use semantic HTML by admax88q on Monday June 07, 2021 @09:58PM (#27429805)

Too true

[ Parent | on HN ]