Re: [w3c/manifest] We should add a character limit to `name` and `short_name` (Issue #1070)

I agree with @marcoscaceres . This feels very much in the domain of UX, not something where the spec should impose arbitrary limits.

If you were to apply the lowest common denominator here, Android's app list truncates names to somewhere between 8 and 12 characters (depending on the font and the width of the individual glyphs). In other contexts, limiting the name to just 8 characters would look quite silly next to other less-truncated names.

The spoofing issue here is that a name would be shown longer in the install / update prompt, than it is in the app list, so two apps that have distinct names at install time have the same name when truncated. The solution to this is that the UI at install time should use the same truncation as the system's app list (if possible), so that the user sees the same thing in both places. That doesn't require spec support.

Similarly, if we're talking about a denial-of-service where an app has a multi-megabyte name or something, the user agent can fix that by truncating it to, say, ~1K, which is longer than any UI will display. You don't need the spec to tell you to do that: you are free to ignore any part of any field you like.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/1070#issuecomment-1418441463
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/1070/1418441463@github.com>