Re: [w3c/manifest] Editorial: add a note on out-of-scope manifest linking behavior (PR #1202)

marcoscaceres left a comment (w3c/manifest#1202)

After discussion with @marcoscaceres, we think this PR's note needs to be paired with normative text, and the note itself revised to be consistent with it.

## Proposed normative text

Add the following to the ["Applying the manifest"](https://w3c.github.io/manifest/#applying) section, after the sentence "the user agent MAY [=apply=] a manifest to it before [=navigate|navigation=] begins":

```html
<p>
  A user agent MAY also [=apply=] a manifest to an existing [=top-level
  browsing context=]. If the [=navigable/active document=]'s
  [=Document/URL=] is [=manifest/within scope=] of the manifest, the
  existing [=top-level browsing context=] becomes an [=application
  context=]. If the [=Document/URL=] is not [=manifest/within scope=],
  the resulting behavior is implementation-defined.
</p>
```

## Revised note

Replace the current `<aside>` added by this PR with the following (and move it to sit directly after the normative text above):

```html
<aside class="note">
  <p>
    Some user agents might [=apply=] a manifest to the existing
    [=top-level browsing context=] from which installation was
    initiated. If the [=navigable/active document=]'s [=Document/URL=]
    is not [=manifest/within scope=] of the manifest's
    [=manifest/navigation scope=], one possible behavior is that the
    [=application context=] initially exists at an out-of-scope
    [=Document/URL=].
  </p>
</aside>
```

## Rationale

- The note previously used `[=launch=]`, which per the spec creates a *new* application context — inconsistent with describing the existing-tab-promotion case.
- The normative text clarifies both branches: in-scope (browsing context becomes an application context) and out-of-scope (implementation-defined).
- Together they close #784 properly: the informative note illustrates one concrete instance of the implementation-defined behavior.

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

Message ID: <w3c/manifest/pull/1202/c4214635261@github.com>