Ian Hickson wrote:
On Thu, 1 Dec 2005, Matthew Raymond wrote:
Thought:
| menu
| li command=cmd_in_head1Menu Item 1/li
| ...
| /menu
Hmm.
That could work. It's an advanced feature though. (Anything involving
indirection is going to be harder for users; the more indirection, the
harder
Ian Hickson wrote:
On Tue, 29 Nov 2005, Matthew Raymond wrote:
Well, what I don't like about this scenario is that we end up with a lot
of different markup in menu:
| menu
| a/
| cmd/
| command/
| li/
| menulabel/
| menu label=/
| /menu
So the situation would be:
menu
Ian Hickson wrote:
My current thinking is to have an attribute on the menu to distinguish
the type of menu, from a list of three types: context menu (hidden until
activated), tool bar/menu bar/menu button/whatever you call it (turns each
command into a button, and each submenu into a menu
On Fri, 2 Dec 2005, Matthew Raymond wrote:
That's not a menu. It's a MENUBAR.
What's the difference?
I would argue that the following are all the same:
* menubars
* pull-down menus
* drop-down menus
* context menus
* toolbars
They're just different presentations of the same underlying
On Wed, 7 Dec 2005, Lachlan Hunt wrote:
I just had a thought that maybe this could be marked up by including
the menu within the head element... However, this would only be
possible in XHTML documents.
Yeah, in HTML it would force the body to open. An option for XHTML,
menu n. A list of available options.
If the definition of menu is too vague then couldn't we include ul and
ol? Especially since people make dynamic menus with these right now.
However, imho ideally the menubar would be powerful enough to turn into
something like MS Office 12's ribbon. When
On Wed, 7 Dec 2005, Matthew Raymond wrote:
menu
command .../
command .../
command .../
/menu
Doesn't the following do the same?
menu
option label=1/
option label=2/
option label=3/
/menu
It does if we say it does.
Why would we do this? I don't
Shipping Safari actually supports hr as separators in select
dropdowns now. We needed this for Dashboard widgets that wanted to
be able to put separators into their select UI.
dave
On Dec 7, 2005, at 4:00 PM, Ian Hickson wrote:
Then again, toolbars often have separators, so maybe
On Thu, 8 Dec 2005, Lachlan Hunt wrote:
I don't really want to add a lot of new attributes to option;
What new attributes are you talking about? Option already has a label
attribute in HTML4.
All the ones that command has.
--
Ian Hickson U+1047E
On Wed, 7 Dec 2005, Nathan Heagy wrote:
menu n. A list of available options.
If the definition of menu is too vague then couldn't we include ul and
ol? Especially since people make dynamic menus with these right now.
ul is an unordered list of items.
ol is an ordered list of items.
Ian Hickson wrote:
On Wed, 7 Dec 2005, Matthew Raymond wrote:
menu
option label=1/
option label=2/
option label=3/
/menu
I don't really want to add a lot of new attributes to option;
What new attributes are you talking about? Option already has a label
attribute in HTML4.
--
David Hyatt wrote:
Shipping Safari actually supports hr as separators in select
dropdowns now. We needed this for Dashboard widgets that wanted to
be able to put separators into their select UI.
Is that inside an option or as a direct child of select?
As a child of a select or optgroup.
dave
On Dec 7, 2005, at 8:47 PM, Matthew Raymond wrote:
David Hyatt wrote:
Shipping Safari actually supports hr as separators in select
dropdowns now. We needed this for Dashboard widgets that wanted to
be able to put separators into their select UI.
13 matches
Mail list logo
