This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html Multipage: http://www.whatwg.org/C#opening-the-input-stream Complete: http://www.whatwg.org/c#opening-the-input-stream Comment: Type argument to Document.open needs to allow "replace" Posted from: 173.48.81.109 by bzbarsky@mit.edu User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:20.0) Gecko/20121203 Firefox/20.0
The behavior of different UAs for the "type" argument of Document.open is as follows: IE and WebKit: Values other than "text/plain" (after truncating at ';'?) are treated as HTML. Opera: Values other than "text/html" are treated as text Gecko: "text/html" and literal (case-sensitive) "replace" are treated as HTML, the rest as text. When we tried doing what Opera does we ran into compat issues back when. See https://bugzilla.mozilla.org/show_bug.cgi?id=313217
Do you have to act as if the fourth argument is also set to "replace" in this situation? (i.e. is it just that the type argument is optional?) Or does it not replace in this situation?
> Do you have to act as if the fourth argument is also set to "replace" in this > situation? No. Not replacing was not a problem in the cases we dealt with. We just treat "replace" as an alias for "text/html" in the third argument and the fourth argument behaves as normal (i.e. not replacing if it wasn't passed).
Checked in as WHATWG revision r7729. Check-in comment: document.open() legacy hack for compat http://html5.org/tools/web-apps-tracker?from=7728&to=7729