when building a css drop-down (<!-- m --><a class="postlink" href="http://www.htmldog.com/articles/suckerfish/dropdowns/">http://www.htmldog.com/articles/suckerfish/dropdowns/</a><!-- m -->)
i allways see them using OL.
why not using the DL tag?A DL list should have pairs of DT and DD elements, while OL/UL lists just contain LI elements. If it make sense for the way your menu is structured to have separate term and description elements for each menu item, then by all means use a DL. But most implementations I've seen just have a list of items, so a UL or OL makes more sense to me.A DL list should have pairs of DT and DD elements, while ... A DT may contain several DD (<!-- m --><a class="postlink" href="http://www.w3.org/TR/REC-html40/struct/lists.html#h-10.3">http://www.w3.org/TR/REC-html40/struct/ ... tml#h-10.3</a><!-- m -->) elements. <!-- w --><a class="postlink" href="http://www.mozilla.org">www.mozilla.org</a><!-- w --> have used definition lists as a menu on some pages.
No reason not to use DL for a menu, although most of the work done on, dropdown, menus is with UL
i allways see them using OL.
why not using the DL tag?A DL list should have pairs of DT and DD elements, while OL/UL lists just contain LI elements. If it make sense for the way your menu is structured to have separate term and description elements for each menu item, then by all means use a DL. But most implementations I've seen just have a list of items, so a UL or OL makes more sense to me.A DL list should have pairs of DT and DD elements, while ... A DT may contain several DD (<!-- m --><a class="postlink" href="http://www.w3.org/TR/REC-html40/struct/lists.html#h-10.3">http://www.w3.org/TR/REC-html40/struct/ ... tml#h-10.3</a><!-- m -->) elements. <!-- w --><a class="postlink" href="http://www.mozilla.org">www.mozilla.org</a><!-- w --> have used definition lists as a menu on some pages.
No reason not to use DL for a menu, although most of the work done on, dropdown, menus is with UL