This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21998 - Why are srcdoc documents not always standards mode?
Summary: Why are srcdoc documents not always standards mode?
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-10 14:22 UTC by contributor
Modified: 2013-06-12 17:53 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2013-05-10 14:22:22 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#the-initial-insertion-mode
Complete: http://www.whatwg.org/c#the-initial-insertion-mode
Referrer: 

Comment:
Why are srcdoc documents not always standards mode?

Posted from: 98.110.194.206
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20130503 Firefox/23.0
Comment 1 Boris Zbarsky 2013-05-10 14:24:00 UTC 
The current setup in the spec requires extra complexity to communicate the "is srcdoc document" boolean to the parser thread where the doctype tokenization is happening, and it's not clear why: are there actual use cases for quirks-mode srcdoc documents, especially given that you have to explicitly opt in with a quirks mode doctype?
Comment 2 Ian 'Hixie' Hickson 2013-05-28 22:32:19 UTC 
Being always standards mode seems reasonable to me.
Comment 3 contributor 2013-06-12 17:53:40 UTC 
Checked in as WHATWG revision r7960.
Check-in comment: make srcdoc docs always be in standards mode
http://html5.org/tools/web-apps-tracker?from=7959&to=7960