Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218)

@Copilot commented on this pull request.

## Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.




<details>
<summary>Comments suppressed due to low confidence (1)</summary>

**index.html:3094**
* Wrap this feature through the privacy note in a `<section id="application-context-media-feature">` and close it before `#priv-sec`, rather than placing the id on a bare heading. Every neighboring top-level heading is contained by a section (`index.html:2933-2936` and `index.html:3274-3277`); this block currently falls outside the document's established semantic section structure.
```
    <h2 id="application-context-media-feature">
      The `application-context` media feature
    </h2>
```
</details>



> +      The <a data-link-for="@media">application-context</a> media feature takes
+      one of the following values:

The normative definition enumerates keywords but never classifies the feature as discrete, even though that classification determines that range/min/max syntax is invalid. Explicitly declaring the range type avoids leaving implementations to infer part of the media-feature grammar.

> +    <aside class="note" title="Not a new information exposure">
+      <p>
+        This media feature does not expose information that authors could not
+        already infer. The <a data-xref-type="css-descriptor" data-xref-for=
+        "@media">`display-mode`</a> media feature already reveals the
+        application context most of the time, since the [=display
+        mode/standalone=] and [=display mode/minimal-ui=] display modes only
+        occur within an [=application context=]. This feature makes that signal
+        explicit and reliable, rather than something authors reconstruct
+        imperfectly from `display-mode`.
+      </p>
+    </aside>

The assertion that no previously unavailable information is exposed contradicts both the following “most of the time” qualification and the feature's purpose: in an application context using `fullscreen` or `browser`, `display-mode` does not identify the context, while this feature does. The privacy assessment should acknowledge that additional observation rather than claiming there is no new exposure.

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

Message ID: <w3c/manifest/pull/1218/review/4768812118@github.com>