- From: Matt Giuca <notifications@github.com>
- Date: Thu, 28 May 2020 23:11:04 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/manifest/pull/880/review/420675844@github.com>
@mgiuca commented on this pull request. > + A <a>manifest</a> can be <dfn data-lt="apply|applying">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. Whenever a <a>top-level browsing context</a> is + created, the user agent MAY <a>apply</a> a manifest to it, before + [=navigate|navigation=] begins. + </p> + <p class="note"> + Whether to [=apply=] a manifest, and which manifest to apply, is at + the discretion of the user agent, based on the user's actions. For + example, if the user launched an application from the system menu or + from a [=launching a shortcut|shortcut=], the user agent might create + a new [=top-level browsing context=] with that application's + [=manifest=] [=applied=], but it might not do so if the user simply + clicked a bookmark to a URL within the application's [=navigation + scope=]. Do you think it's worth pointing that out, Marcos? Seems like a kind of advanced use case that would be allowed, but not sure we need to call it out here. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/pull/880#discussion_r432274544
Received on Friday, 29 May 2020 06:11:17 UTC