Re: [beacon] Random comments

Thanks. It's about the Beacon Spec.
Look at the current processing model at
https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/Beacon/Overview.html#sec-processing-model

Simon suggested changing the processing model to the text pasted below.
Subsequent to that, the question was which "settings" object to use - the
entry settings object or the incumbent settings object. We need you to
answer that question.

[[
2. If the JavaScript global environment is a document environment, run these
    steps:

    1. If settings object's responsible document is not fully active, throw
an
       "InvalidStateError" exception and terminate the overall set of steps.

    2. Set base to settings object's API base URL.

    3. Set source origin to settings object's origin.

   4. Set referrer source to settings object's API referrer source's URL.

3. If the JavaScript global environment is a worker environment, run these
   steps:

    1. Set base to settings object's API base URL.

    2. Set source origin to settings object's origin.

    3. Set referrer source to settings object's API referrer source.
]]



On Wed, Feb 12, 2014 at 10:58 AM, Ian Hickson <ian@hixie.ch> wrote:

>
> Sorry, I apparently missed this thread the first time around.
>
> On Tue, 11 Feb 2014, Arvind Jain wrote:
> >
> > Simon:
> > Hmm. HTML APIs mostly use
> http://www.whatwg.org/specs/web-apps/current-work/
> > multipage/webappapis.html#incumbent-settings-object although that's
> > different to XHR. If we want like XHR you can say the context object's
> > document's global object's settings object (phew), or some such. But I'm
> > not sure which is better. Anne, Hixie?
>
> I don't understand the question. What are we trying to do here? Is there
> specific spec text to review?
>
> --
> Ian Hickson               U+1047E                )\._.,--....,'``.    fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
>