- From: Daniel Murphy <notifications@github.com>
- Date: Mon, 30 Sep 2024 09:00:47 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/manifest/issues/1070/2383597663@github.com>
@aphillips > You may wish to refer to this section of [Best Practices for International Specs](https://www.w3.org/TR/international-specs/#char_truncation) for more info on length limitations. Super interesting! Thanks for this. I'm guessing we COULD specify some large limit for physical storage on disk that hopefully shouldn't affect practically affect anything - (4kb for each?) The main thing I'm concerned about / we've had to deal with: The main limitation here is the physical size of, say, the UX element. E.g. the 'uninstall' dialog needs to show the app name. Sometimes UX elements have fancy eliding functionality, but other times (and in Chromium usually for our browser UX) we have to pre-process the text to elide the physical length. I found the [place](https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/ui/browser.cc;l=891;drc=f522344e45882da4c7f7cb1b3a0a7bd747d654bb;bpv=1;bpt=1) we do this in Chromium for tab titles. Do you know if there are specifications around doing physical truncations-plus-ellipsis based on pixel width available? If not, we can easily put non-normative text that a UA may limit / elide `short_name` to <hopefully example N> pixel width for dialogs, and same for `name`. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/1070#issuecomment-2383597663 You are receiving this because you are subscribed to this thread. Message ID: <w3c/manifest/issues/1070/2383597663@github.com>
Received on Monday, 30 September 2024 16:00:51 UTC