Re: Menuitem's content model

Self-reply to my previous message, only to summarize the subject, hoping
that someone can either make a change or explain why the change is not
wanted.
Proposal summary:
1. menuitem, as void element, is not compatibe with unsupporting browsers.
The resulting DOM subtree has subsequent menuitem elements nested inside
the previous ones.
2. validator.w3.org/nu flags as error the use of menuitem as void element,
reporting that the closing tag is missing. My previous bug reports about
this behavior has received the same answer of my previous message in this
thread: nothing.
3. once that the error of considering menuitem as void has been corrected,
it could be thought to allow text content inside this element as proper
label for the command, in a way similar to the option element. This is not
part of the necessary fix for the error, but I believe that authors prefer
to use text nodes rather than attribute in order to display visible
writings.

I hope to receive your answers and opinions for discussing them, even if it
means that I missed any point.
Regards.
Andrea