Re: [w3c/manifest] Redefine application context on top-level traversable (PR #1219)

@Copilot commented on this pull request.

## Pull request overview

Updates the Web App Manifest spec terminology to align the “application context” lifecycle with HTML’s navigable model by anchoring it on a **top-level traversable** (instead of a top-level browsing context), and introduces an explicit “unapply” transition.

**Changes:**
- Redefines “apply/applying” to target a **top-level traversable** and updates the “application context” definition accordingly.
- Adds an “unapply/unapplying” definition to explicitly describe when an application context ceases.
- Simplifies “create a new application context” to apply the manifest to, and return, the traversable directly.






---

💡 <a href="/w3c/manifest/new/main?filename=.github/instructions/*.instructions.md" class="Link--inTextBlock" target="_blank" rel="noopener noreferrer">Add Copilot custom instructions</a> for smarter, more guided reviews. <a href="https://docs.github.com/en/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot" class="Link--inTextBlock" target="_blank" rel="noopener noreferrer">Learn how to get started</a>.

>            The [=manifest's=] <code><dfn data-export="" data-dfn-for=
           "manifest">orientation</dfn></code> member is a <a>string</a> that
           serves as the <a>default screen orientation</a> for all <a>top-level
-          browsing contexts</a> of the web application. The possible values are
+          traversables</a> of the web application. The possible values are
           those of the {{OrientationLockType}} enum, which in this

This section still contains an occurrence of “top-level browsing context” later in the `orientation` member prose (currently around lines 728–729). To complete the terminology migration and avoid mixed models in the same section, update that reference to “top-level traversable” as well.

>          A user agent can provide a way for the end-user to <dfn class="export"
         data-lt="installed|installing|installation">install</dfn> a web
         application on the end-user's device, allowing the user to instantiate
-        a new [=top-level browsing context=] with the manifest's members
+        a new [=top-level traversable=] with the manifest's members
         [=applied=].

There’s still a reference to “top-level browsing context” in the installation note just after this paragraph (currently around lines 2640–2641: “applied … to the top-level browsing context”). For consistency with the rest of this PR’s terminology update, that note should be updated to “top-level traversable”.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/1219#pullrequestreview-4354651313
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/pull/1219/review/4354651313@github.com>