- From: Michael(tm) Smith <mike@w3.org>
- Date: Tue, 29 Jun 2010 16:13:32 +0900
- To: www-math@w3.org
If you have use cases and/or real-world examples, in existing documents, of <annotation-xml> instances containing HTML content, please post them as replies to this message and/or as comments to the following HTML WG bugzilla bug - http://www.w3.org/Bugs/Public/show_bug.cgi?id=9887 The background on my request is this: - The HTML5 specification defines an algorithm for parsing text/html (non-XML) documents that contain MathML elements. - That algorithm deals with the <annotation-xml> element as a special case; it provides for both SVG and MathML content in <annotation-xml> being properly parsed into a DOM as expected. - However, for the case of HTML content in <annotation-xml>, it does not provide for that content getting into the DOM as child content of the <annotation-xml> element; instead such content will essentially end up getting into the DOM as a following sibling of any ancestor <math> element. You can test and see for yourself by using a recent Mozilla Minefield or Firefox nightly build with this page: http://software.hixie.ch/utilities/js/live-dom-viewer/ for example: http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Ctitle%3E%3C%2Ftitle%3E%0A%3Cp%3E%0A%3Cmath%3E%0A%3Csemantics%3E%0A%3Cmi%3Efoo%3C%2Fmi%3E%0A%3Cannotation-xml%3E%0A%3Cimg%20src%3Dbar%3E%0A%3C%2Fannotation-xml%3E%0A%3C%2Fmath%3E%0A%3C%2Fp%3E or: http://bit.ly/dy4Rxj So what I would like to try to get clarification on is whether there are compelling use cases for having HTML content within the <annotation-xml> element that would justify making a change at this point to the parsing algorithm in the HTML5 spec (and to the behavior of existing implementations of that). --Mike -- Michael(tm) Smith http://people.w3.org/mike
Received on Tuesday, 29 June 2010 07:13:37 UTC