W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > December 2012

[Bug 20390] The origin of documents not in a browsing context is wrong in the spec

From: <bugzilla@jessica.w3.org>
Date: Wed, 19 Dec 2012 19:38:58 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-20390-2532-79x0WxFeH4@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20390

--- Comment #10 from Boris Zbarsky <bzbarsky@mit.edu> ---
What Gecko does is use an alias to the origin and effective script origin of
the Window (which is NOT the same as using the origin and effective script
origin, note; I believe the alias thing is what we want).

In gecko, the origin and effective script origin of a Window alias the origin
and effective script origin of its associated document while it has a document.
 When it loses the document (unloaded, frame removed from DOM, document.open(),
whatever) it continues to alias that no-longer-associated document's origin and
effective script origin.  If in the spec Windows never end up in a state where
they have no associated document, then the spec can just talk about aliasing
the associated document.

> Note that DOM just defines a default being a globally unique identifier, but
> also defines that for new Document(), createDocument(), and
> createHTMLDocument(), that is overridden

That makes sense to me.

In all three of those cases we should, imo, alias the origin and effective
script origin of the document involved (the associated document of the Window
for the constructor, and the document the DOMImplementation came from for the
other two).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 19 December 2012 19:39:01 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:04:28 UTC