- From: <bugzilla@jessica.w3.org>
- Date: Tue, 16 Oct 2012 20:08:46 +0000
- To: public-html-bugzilla@w3.org
- Message-ID: <bug-13409-2486-pJBBvnbe4m@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13409 Sam Ruby <rubys@intertwingly.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rubys@intertwingly.net --- Comment #23 from Sam Ruby <rubys@intertwingly.net> --- Test case: http://intertwingly.net/tmp/bug13409.xhtml Current status is that the latest release of Opera will resolve the § entity reference, and that the latest releases of IE, Firefox, Safari, and Chrome will not. Given this, do we have any reason to believe that if the spec were to change in the manner described by this bug report that this behavior will meet the published exit criteria for the HTML WG: http://dev.w3.org/html5/decision-policy/public-permissive-exit-criteria.html The reason why I ask is that adding it now just to remove it later is not a good use of our collective time. -------------------------------------- Chair hat off: re: "it would be preferable if the html5 entity definitions were also loaded for the standard HTML5 doctype declaration <!DOCTYPE html> or all doctypes" doctypes like application/xhtml+xml or application/xml should be processesable via standard XML toolchains. This would not be the case if the proposal were adopted. Example: $ python Python 2.7.2+ (default, Jul 20 2012, 22:15:08) [GCC 4.6.1] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from xml.dom import minidom >>> from urllib import urlopen >>> minidom.parse(urlopen('http://intertwingly.net/tmp/bug13409.xhtml')) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python2.7/xml/dom/minidom.py", line 1914, in parse return expatbuilder.parse(file) File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 928, in parse result = builder.parseFile(file) File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 207, in parseFile parser.Parse(buffer, 0) xml.parsers.expat.ExpatError: undefined entity: line 9, column 7 -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 16 October 2012 20:08:49 UTC