- From: Daniel Murphy <notifications@github.com>
- Date: Thu, 13 Aug 2026 10:47:58 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 13 August 2026 17:48:02 UTC
dmurph left a comment (w3c/manifest#1228) User agents often display these strings in UX, and also provide these strings to the OS, and recently we have been dealing with trying to button issues like this where the UX could get messed up with malformed / unpaired / weird utf stuff. So I don't think it's necessarily a bad thing if the spec defined stuff around discarding these? I'm not sure if using USVString does that, or we would have to say we do that? Is that the norm for using a USVString? where you want to sanitize it for UX reasons? -- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/1228#issuecomment-5284335995 You are receiving this because you are subscribed to this thread. Message ID: <w3c/manifest/issues/1228/5284335995@github.com>
Received on Thursday, 13 August 2026 17:48:02 UTC