- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 22 Sep 2009 19:49:47 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7473 Jim Jewett <jimjjewett@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jimjjewett@gmail.com --- Comment #2 from Jim Jewett <jimjjewett@gmail.com> 2009-09-22 19:49:47 --- It is more clear than it was a few months ago, but ... no, it still isn't as obvious as it should be, because the HTML spec is still making changes and clarifications to MathML and SVG as part of the embedding. For example, in section 3.1.4: "HTML, SVG, and MathML elements define which classes they are in" or section 4.8.15 MathML: "User agents must handle text other than inter-element whitespace found in MathML elements whose content models do not allow straight text by pretending for the purposes of MathML content models, layout, and rendering that that text is actually wrapped in an mtext element in the MathML namespace." Given this, I believe it is appropriate to state that the svg and math elements (and their children) -- even when embedded in a HTML document -- get all their semantics (explicitly including their aria-* semantics) from the respective standards. In 4.8.15 and 4.8.16 it is enough to say that the semantics are unchanged. In the aria pullout section (3.2.6) there is an implication that all aria/native semantics needed for a HTML agent are grouped together. It should be explicit that this is not the case, because there may be additional semantics coming from the MathML or SVG specs. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Tuesday, 22 September 2009 19:49:58 UTC