This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
for example we have: 1) Command: an element that defines a command, whose Type facet is "checkbox", and that is a descendant of a menu element whose type attribute is in the toolbar state 2a) input (type attribute in the Checkbox state and parent is a menu) 2b) menuitem (type attribute in the Checkbox state) it looks like that 1 dupes 2a and 2b, having 2a and 2b should be enough. Agree?
(In reply to comment #0) > for example we have: > > 1) Command: an element that defines a command, whose Type facet is > "checkbox", and that is a descendant of a menu element whose type attribute > is in the toolbar state > > 2a) input (type attribute in the Checkbox state and parent is a menu) > 2b) menuitem (type attribute in the Checkbox state) > > it looks like that 1 dupes 2a and 2b, having 2a and 2b should be enough. > Agree? It's not clear to me, but is it not possible to have an <option> element that is a descendant of <menu type="toolbar"> and that defines a checkbox command? If not, then I agree. If so, then perhaps we just add an extra entry for such an <option> element and remove the "Command:..." entry for the checkbox facet? Can we do the same with "Command:..." entry for the radio facet? Am I right in thinking we still need to keep the entry for "Command:..." with a command facet?
I think my primary concern is to keep commands stuff under elements section. Probably it'd be good to have a separate section for commands like we have for attributes. Or like you said list all elements that can be used to define a command.