- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Thu, 14 Jun 2012 11:49:55 +0200
- To: Elliott Sprehn <esprehn@gmail.com>
- Cc: Ryosuke Niwa <rniwa@webkit.org>, www-dom <www-dom@w3.org>, Ojan Vafai <ojan@chromium.org>, Boris Zbarsky <bzbarsky@mit.edu>
On Wed, Jun 13, 2012 at 7:47 PM, Elliott Sprehn <esprehn@gmail.com> wrote: > So it seems the one element, one doctype rule is already pretty well > enforced. And why do we not want to enforce ordering? I'm not entirely sure what the goal is here. > I'd like to change the spec so that instead of requiring a specific > ordering, it requires that the serialization of the document (for example > through XMLSerializer) always reflects the current document state, even if > you removed the doctype node entirely. That ensures that serializing a live > document gets you something that would render the same a second time. So HTML documents would always get the same doctype in standards mode, the same doctype in almost standards mode, and the same doctype (or maybe lack of) in quirks mode? Would that only happen if the doctype was meddled with? What about XML documents? What is the processing model going to be? -- Anne — Opera Software http://annevankesteren.nl/ http://www.opera.com/
Received on Thursday, 14 June 2012 09:50:29 UTC