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

Re: Re: [XHR] Associating XHR instances with documents - clarify spec statement in 4.6.1

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 22 Nov 2012 14:25:46 +0100
Message-ID: <CADnb78hjYGJbAVjxoeFoTEYejPJ5fFOCDkkrKYrNUsAiOVHSPg@mail.gmail.com>
To: Hallvord Reiar Michaelsen Steen <hallvord@opera.com>
Cc: Jungkee Song <jungkee.song@samsung.com>, Julian Aubourg <j@ubourg.net>, public-webapps@w3.org
On Thu, Nov 22, 2012 at 2:14 PM, Hallvord Reiar Michaelsen Steen
<hallvord@opera.com> wrote:
>> You'd also need to check the JavaScript global environment.
>
> Thanks for responding. How?

Just like the spec does now?


>> What I mean is that <var>-variables are scoped to the algorithm they
>> are used in. So you need to re-introduce <dfn
>> title=concept-XMLHttpRequest-document>document</dfn> or some such.
>
> Ah, OK. We already have an instance property named "referrer source", which is a somewhat obscure name but does reference the document. Can we just re-name "referrer source" => "associated document" or something, and set it in constructor, then use it for the "not fully active" check etc in open() ?

No, see below.


> (Naming it "referrer source" re-uses terminology from CORS or Workers? I believe it will always refer to a document - in "web worker mode" the document associated with the script - and we can say "use associated document as *override referrer source* when referencing CORS algorithm. IMO this is easier to understand in the context of this spec.)

Referrer source is from HTML and can be a URL. I prefer to keep that
name consistent throughout all specifications.


-- 
http://annevankesteren.nl/
Received on Thursday, 22 November 2012 13:26:20 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:56 GMT