- From: Marcos Caceres <notifications@github.com>
- Date: Fri, 19 Dec 2014 21:22:20 -0800
- To: w3c/manifest <manifest@noreply.github.com>
- Message-ID: <w3c/manifest/pull/289/r22140047@github.com>
> + <section> > + <h3 id="applying"> > + Applying the manifest > + </h3> > + <p> > + A <a>manifest</a> is <dfn>applied</dfn> to a <a>top-level browsing > + context</a>, meaning that the members of the <a>manifest</a> are > + affecting the presentation or behavior of a browsing context. > + </p> > + <p> > + A <a>top-level browsing context</a> that has a manifest applied to it > + is an referred to as <dfn>application context</dfn>. > + </p> > + <p> > + When an <a>application context</a> is created, the user agent MUST > + immediately <a>navigate</a> to the <a>start URL</a> with <a href= Sure, but that's different to the requirement here. What this is actually saying is the user agent MUST: 1. create a browsing context. 2. set it to "about:blank". 3. immediately try to load the start url AND trash the history, so there is no record of "about:blank". What happens after that is whatever HTML5 allows. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/pull/289/files#r22140047
Received on Saturday, 20 December 2014 05:22:46 UTC