Menu/Toolbars/Table of Contents in 8th October Editors Draft

A wish for a facility to build a reuseable/callable "Table of Contents" Toolbar 
to navigate across Documents. I currently reuse an include file, but this means 
I sacrifice identifying the current page - though other cues such as 
filename/title are available.

It seems that there are a few (perhaps too many) ideas integrated into the 
current menu section.
<http://www.w3.org/html/wg/html5/#menus>

I'd like to be wrong, in surmising from the following text,
that the proposed toolbar is "always visible [only within a page]"
as demonstrated at <http://www.w3.org/Style/Examples/007/menus>.
> 
> 3.18.4.4. Toolbars
> 
> Toolbars are a kind of menu that is always visible.
> 
> When a menu element has a type attribute with the value toolbar, then the user agent must build the menu for that menu element and render it in the document in a position appropriate for that menu element.
> 
> The user agent must reflect changes made to the menu's DOM immediately in the UI. 

Perhaps the element should be called a "Toolbar" to distinguish it from a "menu" 
list  demonstrated by <http://www.visionaustralia.org.au/> who uses an 
Unnumerated List and a style sheet for their menus - if we are adopting the 
principles of paving the cowpaths  in HTML5 this would look something like:

<menu id="topnav">
<li class="current">Home</li>
<li><a href="/info.aspx?page=674">About Us</a></li>
<li><a href="/info.aspx?page=587">Services</a></li>
...
</menu>

In which case, the menu has to be recoded for each webpage and adding an option 
is a problem. I would like to be able to identify the current page in a 
menu/table of contents.

Menu items seem to have a bit in common with items in ordered and unnumbered 
list to warrant "3.18.5. Commands" and the reset/submit form functions can these 
be grouped.

Marghanita
-- 
Marghanita da Cruz
http://www.ramin.com.au
Phone: (+61)0414 869202

Received on Tuesday, 9 October 2007 06:28:40 UTC