First of all, my suggestion is that submenus always have an
associated menulabel.
I've taken menulabel to be a text label specifically and wonder
about menus opened from an icon-only, such as would be found on a
toolbar.
--
Nate
---
heagy.com
On 12/13/05, Matthew Raymond [EMAIL
Nate H. wrote:
I'm guessing nesting a select within another select will break current UAs.
Sub-menus like that will be handled with nested optgroup elements.
--
Lachlan Hunt
http://lachy.id.au/
Nate H. wrote:
First of all, my suggestion is that submenus always have an
associated menulabel.
I've taken menulabel to be a text label specifically and wonder
about menus opened from an icon-only, such as would be found on a
toolbar.
I think it's up to the user agent to decide what
On Tue, 13 Dec 2005, Matthew Raymond wrote:
First of all, my suggestion is that submenus always have an associated
menulabel.
So what do you do when there isn't one?
FWIW, I propose that a menu with no title inside another menu just ends up
treated as if it had a separator each side. As
Ian Hickson wrote:
How about:
form action=redirect.cgi
menu type=commands
menu label=Select site...
select name=goto
onchange=if (this.options[this.selectedIndex].value)
location = this.options[this.selectedIndex].value
option
On Tue, 13 Dec 2005, Alexey Feldgendler wrote:
I think there's nothing wrong in using the menus for navigation except
that such a solution makes an impression of something presentational
rather than semantic.
No more so, IMHO, than a paragraph of a links, or a ulist of a
links, is
On Tue, 13 Dec 2005, Nate H. wrote:
First of all, my suggestion is that submenus always have an
associated menulabel.
I realise you've made that assumption but I'm not sure that icon-only
menus/toolbars would work that way.
The icon-only-ness of a menu is a presentational detail. Even
On Wed, 14 Dec 2005, Sander Tekelenburg wrote:
Personally I wouldn't mind upgrading LINK to something that user-agents
must support :)
The spec can require whatever it likes, that won't in any way make
browsers support things. :-)
But then still, until they all do, authors will have to
Ian Hickson wrote:
On Wed, 14 Dec 2005, Sander Tekelenburg wrote:
But then still, until they all do, authors will have to continue
providing in-body navigational content.
One of the key concepts Tantek often pushes in the microformats forums is
the idea that metadata should be visible. link
On Thu, 15 Dec 2005 04:31:05 +0600, Lachlan Hunt
[EMAIL PROTECTED] wrote:
I'm guessing nesting a select within another select will break
current UAs.
Sub-menus like that will be handled with nested optgroup elements.
Are current browsers ready for nested optgroup?
-- Opera M2 9.0 TP1
On Thu, 15 Dec 2005 06:42:37 +0600, Ian Hickson [EMAIL PROTECTED] wrote:
One possible solution that comes to my mind is describing a site map
with some tree of nested elements, with page titles, URIs and other meta
information, but without any presentational information. As this site
map is
11 matches
Mail list logo
