Re: [w3c/manifest] First pass as adding a Client Hint for Display Mode (#977)

@tomayac commented on this pull request.



> +        rendered in order to make content-negotiation decisions. Though this
+        information is accessible via JavaScript, when sent as part of a
+        {{Request}}, servers are empowered to do the content-negotiation
+        earlier in the process of setting up the web app, before JavaScript
+        execution takes place. To convey this information, this document
+        provides for the following <a data-cite=
+        "client-hints-infrastructure#client-hint-token">client hint token</a>:
+      </p>
+      <ul>
+        <li>`Sec-CH-Display-Mode` whose value is a suitable [=display modes
+        value=]
+        </li>
+      </ul>
+      <section>
+        <h3>
+          The 'Sec-CH-Display-Mode' Header Field

`Sec-CH-*` is the common prefix for such hints sent by the user agent over secure connections (display mode being `standalone` depends on the PWA to be installed). Also see [User Preference Media Features Client Hints Headers](https://tomayac.github.io/user-preference-media-features-headers/) that we're specifying at the moment. 

-- 
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/977#discussion_r629859824