4 msΒ·
Funny how it triggered a bug in Firefox. When the tab is unfocused, its title in the handle is "πΌπβ¦", but when it gets the focus it becomes "πΌ<D835>β¦" (in a
by emillon 12y ago
Funny how it triggered a bug in Firefox. When the tab is unfocused, its title in the handle is "πΌπβ¦", but when it gets the focus it becomes "πΌ<D835>β¦" (in a square box). The next codepoint is U+1D48F whose UTF-16 BE encoding is d8 35 dc 8f.
I'd say that the truncation algorithm operates on bytes and that it can't make sense of d8 35, but I'm not too sure how to fix that since graphemes can have arbitrary length (right?). Do you have to compute the width in advance?
- jabiko 12y agoIt seems like this is a known bug: https://bugzilla.mozilla.org/show_bug.cgi?id=921528 https://bugzilla.mozilla.org/show_bug.cgi?id=921528
- anon1385 12y agohttp://www.unicode.org/reports/tr29/ http://www.unicode.org/reports/tr29/ There are libraries for doing it in Javascript: https://www.npmjs.org/package/grapheme-breaker https://www.npmjs.org/package/grapheme-breaker (is that part of the Firefox UI done in Javascript? I've no idea)
- pwnna 12y agoHm.. i'm on nightly and seems to be unaffected by this problem.
- emillon 12y agoIt depends on the size of the tab headers.
- pc86 12y agoI am using FF Dev Edition and see "Unico<D835>..." regardless of focus. Weird.
- aninhumer 12y ago>I'd say that the truncation algorithm operates on bytes This seems likely, as another notable weirdness is that even with full width tabs, where there's plenty of space for at least "πΌπππππ π π»πππ..." it still only shows "πΌππππ...".