- From: <bugzilla@jessica.w3.org>
- Date: Tue, 13 May 2014 21:49:09 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23170 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ian@hixie.ch --- Comment #14 from Ian 'Hixie' Hickson <ian@hixie.ch> --- (In reply to Morrita Hajime from comment #12) > Thinking a bit more about the implication of this change: > > * 1. Forms become submittable > * 2. Frames will be loaded > * 3. Media (audio, video) and plugins are also loaded. None of these are defined in terms of defaultView. Forms are submittable if their Document has a browsing context. A browsing context can only have one active document at a time, that's the one that's being rendered. It's the one you get from Window.document. If we change this and let Windows have multiple "child" Documents, then things are going to get really weird really quickly. For example, window.onload will fire when any of the child Documents finish loading. The Window object's supported property names would presumably come from all of its child documents, which would lead to all kinds of weird conflicts (e.g. what if two documents have elements with id="thetop"?). Things like window.location would return... what? The number of things in the platform that assume a 1:1 mapping of Window:Document is high. Just the weirdness around document.open Document reuse and about:blank Window reuse is confusing enough... -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 13 May 2014 21:49:11 UTC