- From: <bugzilla@jessica.w3.org>
- Date: Wed, 01 Feb 2012 09:31:08 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13409 --- Comment #15 from David Carlisle <davidc@nag.co.uk> 2012-02-01 09:31:02 UTC --- (In reply to comment #14) > Adding new DTDs is not backwards-compatible and provides no new abilities, > hence the requirement that they be already-supported DTDs. I'm sorry Ian, but that description just doesn't match the reality of the situation. The description of any DTD in that list being "new" is highly mozilla-specific, and doesn't even match mozilla's behaviour. pre html5 only mozilla based browsers special cased the mathml dtd PUBLIC IDs in that way, IE (in its xml parsing mode) fetched any specified dtd and others (as far as I know) didn't fetch the mathml ones. Mozilla's list as implemented included useful version-agnostic dtd support in addition to the list of PUBLIC ids, as it special cased any dtd that had "mathml" in its SYSTEM ID. This is why the MathML 2 and MathML3 specs used to render perfectly OK, but now give fatal parse errors. I don't see how you could cause that to happen, then claim "backward compatibility" as an excuse for not fixing it. -- Configure bugmail: https://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 Wednesday, 1 February 2012 09:31:10 UTC