- From: Daniel Murphy <notifications@github.com>
- Date: Thu, 29 Jul 2021 15:15:25 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 29 July 2021 22:15:37 UTC
@dmurph commented on this pull request. This change looks good, but as @marcoscaceres referenced - we don't have signals from other vendors. If we need a place for this spec to live in the meantime we can put it in manifest-incubations > + <h3> + The 'Sec-CH-Display-Mode' Header Field + </h3> + <p> + The <dfn data-export="" data-lt= + "display mode client hint">Sec-CH-Display-Mode</dfn> request header + field gives a server information about the [=display mode=] in which + the user agent plans to display the web app. It is a <a data-cite= + "rfc8941#section-3">Structured Header</a> whose value MUST be a valid + <a data-cite="rfc8941#section-3.3.3">string</a>. + </p> + <p> + The header's ABNF is: + </p> + <pre> + Sec-CH-Display-Mode = sf-string I think we would also want to have this possibly be values that end up in manifest-incubations spec - not sure the best way to do this spec-wise, but referencing display-mode is probably a good way. -- 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#pullrequestreview-718576607
Received on Thursday, 29 July 2021 22:15:37 UTC