- From: Dominic Farolino <notifications@github.com>
- Date: Tue, 14 Jul 2026 06:23:17 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 14 July 2026 13:23:21 UTC
domfarolino created an issue (w3c/manifest#1228) I'm reviewing a spec that references a manifest's [name](https://w3c.github.io/manifest/#dfn-name), and makes use of it in IDL. Should the IDL type corresponding to this be a DOMString or a USVString? For that matter, should the actual type of this member in the spec be a USVString, or a traditional infra string as it is now? My understanding is that: - USVStrings are required for data displayed in native windows, per https://w3ctag.github.io/design-principles/#idl-string-types. - That JSON can technically have unpaired surrogates that don't comprise a code point, and thus the infra string cannot be safely displayed in native interfaces Am I correct in thinking that perhaps the manifest name (and other displayable, or URL components of a manifest) should be represented by a USVString, as should other specs referencing these types or holding onto them in IDL? -- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/1228 You are receiving this because you are subscribed to this thread. Message ID: <w3c/manifest/issues/1228@github.com>
Received on Tuesday, 14 July 2026 13:23:21 UTC