> Here[1] you can see that the standard places no restrictions on what can be entered in the <meta> name option
Just because the standard places no restriction on it doesn't mean it's a good idea.
> doing a CSS hack
Setting a CSS property is not a hack.
> so that your <menu> hack
Using existing, well-defined elements whose purpose perfectly fit the needs of the situation is not a hack.
> is worse than doing the standards-compliant method of implementing the browser-specific feature via the meta tag.
There is nothing non-standard-compliant about using a <menu> object for defining a menu.
I don’t think you understand what “CSS hack” means.
Re:Microsoft, Please Stop This Madness
by Locke1689 on Monday September 20, 2010 @02:15PM
(#1709899)
By hack I meant workaround to overload the original function of the CSS menu tag to replicate the function of the <meta> tag. The <meta> tag is explicitly meant to represent metadata about the page. The <menu> tag is explicitly meant to represent a menu in the page.
Here[1] you can see that the standard places no restrictions on what can be entered in the <meta> name option and the browser is not required to implement handlers for all names. Given that this is not display HTML, I think the <meta> tag is the perfect place for this.
[1] http://www.whatwg.org/specs/web-apps/current-work/#attr-meta...