7473 2009-08-31 19:42:56 +0000 JimJJewett gmail: Mention explicitly that the mapping for foreign content -- including adopted MathML or SVG -- is left to those working groups. (Otherwise, I would have expected some strong native semantics for math to math) 2010-10-04 14:55:40 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All VERIFIED FIXED http://whatwg.org/specs/web-apps/current-work/#annotations-for-assistive-technology-products NoReply P3 normal LC 1 contributor ian jimjjewett mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 26760 0 contributor 2009-08-31 19:42:56 +0000 Section: http://whatwg.org/specs/web-apps/current-work/#annotations-for-assistive-technology-products Comment: JimJJewett gmail: Mention explicitly that the mapping for foreign content -- including adopted MathML or SVG -- is left to those working groups. (Otherwise, I would have expected some strong native semantics for math to math) Posted from: 32.97.110.60 27453 1 ian 2009-09-21 23:58:47 +0000 You want the HTML spec to say that mappings for MathML and SVG, if any, are to be found in the specs for those languages? Isn't that obvious? Why would the HTML spec say anything at all about other languages, other than where they integrate with the parsing and content models? 27567 2 jimjjewett 2009-09-22 19:49:47 +0000 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. 27582 3 contributor 2009-09-22 21:29:24 +0000 Checked in as WHATWG revision r3976. Check-in comment: Mention that MathML and SVG semantics are defined in their relevant specs. http://html5.org/tools/web-apps-tracker?from=3975&to=3976 27583 4 ian 2009-09-22 21:29:33 +0000 Ok, I added a note to the MathML and SVG sections saying that their specs define their semantics. I haven't mentioned anything explicitly about ARIA because it seems like that would be implied by the above. 33373 5 mjs 2010-03-14 14:50:29 +0000 This bug predates the HTML Working Group Decision Policy. If you are satisfied with the resolution of this bug, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment. 33559 6 jimjjewett 2010-03-15 04:14:20 +0000 I would still prefer a note in the ARIA section that the ARIA requirements for SVG and Math elements are still defined by those specs, even when the elements are profiled by HTML.