- From: <bugzilla@jessica.w3.org>
- Date: Wed, 02 Apr 2014 16:34:45 +0000
- To: public-html-admin@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25233
Bug ID: 25233
Summary: Specify that "Optionally, a DOCTYPE” means that quirky
doctypes must be ignored
Product: HTML WG
Version: unspecified
Hardware: PC
URL: http://www.w3.org/html/wg/drafts/html/master/embedded-
content.html#attr-iframe-srcdoc
OS: All
Status: NEW
Severity: normal
Priority: P3
Component: HTML5 spec
Assignee: dave.null@w3.org
Reporter: xn--mlform-iua@xn--mlform-iua.no
QA Contact: public-html-bugzilla@w3.org
CC: mike@w3.org, public-html-admin@w3.org,
public-html-wg-issue-tracking@w3.org
This issue is related to bug 25232.
SITUATION:
For docs inside @srcdoc, spec says that the DOCTYPE is optional:
http://www.w3.org/html/wg/drafts/html/master/single-page.html#attr-iframe-srcdoc
Thus, DOCTYPE is not required for @srcdoc documents.
But what should the parser do if there is a *quirky* DOCTYPE inside the
@srcdoc? Should it ignore the DOCTYPE? Or should it render the document in
quirks mode?
PROPOSAL:
We should take same attitude to this as we have taken to UTF-8. Thus, qurks
mode should *not* be spread to new contexts. Therefore, spec should point out
that "Optionally, a DOCTYPE" means that the DOCTYPE is to be ignored and thus,
that the iframe document is to be rendered in no-quirks mode.
IMPLEMENTATIONS:
* Firefox implements the proposed behavior
* Webkit and Blink (at least current release of Safari and Chrome) places the
docuent in no-quirks mode if the DOCTYPE is lacking. However, if there is a
quirky doctype, then they put the document in quirks mode.
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 2 April 2014 16:34:46 UTC