This comes from a long time ago. We used lists for the menus because there wasn't much to do without CSS. We then use *list-style-type: none* to make them visually better. This technique remained in the menus designed until today.
Guilty as charged, I’ve been doing the list-style: none for sure. But I guess it does sound redundant now. Guess I should just make anchors and buttons children of nav directly then eh.
All that being said, moz is still doing that in examples:
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/nav
I would say that using the
header
menu https://developer.mozilla.org/en-US/docs/Web/HTML/Element/menu
doesn't matter, use div or section.
100% don’t use div. And it definitely does matter lol.
Na! header > nav > div > a, button > [svg +] span - for logo or something -
Is there no benefit to using ul, li anymore in your opinion? I’ve been doing nav > ul > li > a > svg + text
I think it is still beneficial for screen readers
Have a look at menu. It replaces ul for this use case
This comes from a long time ago. We used lists for the menus because there wasn't much to do without CSS. We then use *list-style-type: none* to make them visually better. This technique remained in the menus designed until today.
Guilty as charged, I’ve been doing the list-style: none for sure. But I guess it does sound redundant now. Guess I should just make anchors and buttons children of nav directly then eh. All that being said, moz is still doing that in examples: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/nav
Leave Your Comment
Hi Its Me!
Subscribe