Hyphenation (CSS hyphens: auto) not optimal
Reported by
m...@thomasbachem.com,
Dec 28 2016
|
||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.28 Safari/537.36 Steps to reproduce the problem: The attached test case shows that words are not hyphenated in an optimal way in Chrome and Safari compared to Firefox and IE/Edge. What is the expected behavior? The word "infrastructure" should be hyphenated as "infrastruc-ture", not "in-frastructure". What went wrong? From my testing, this doesn't seem to be a dictionary issue, but rather a non-optimal hyphenation strategy. Did this work before? No Does this work in other browsers? N/A Chrome version: 56.0.2924.28 Channel: beta OS Version: OS X 10.11.2 Flash Version:
,
Jan 5 2017
It looks like the Mac hyphenation dictionary has: in-frastructure I checked the OS X API return values in the debugger, but Safari breaking the same way confirms that this is an OS issue. Note, Firefox uses its own dictionaries, not the one in OS X, so it's possible they do it differently. If you think this is wrong for English hyphenations, can you please report this to Apple? > From my testing, this doesn't seem to be a dictionary issue, but rather a non-optimal hyphenation strategy. If you have reasons to believe so, please let me know.
,
Jan 5 2017
Sorry, I should have added another test case to show why I came to that conclusion. Find it attached now. If only the word "infrastructure" gets hyphenated alone, there are many more breakpoints.
,
Jan 5 2017
I also observed that with many other words btw, which would mean that Apple's dictionaries are really bad.
,
Jan 6 2017
#3: thank you, yeah, that looks weird. Let me re-open.
,
Jan 6 2017
So here's what's happening. OS X hyphenation API returns: "infrastructure" -> "in-frastructure" "frastructure" -> "fras-tructure" "tructure" -> "truc-ture" So you can get all these points hyphenated, but you can't get "infrastruc-ture". Could you please report this to http://bugs.webkit.org, or to Apple developer program if you're member of? Chrome will automatically get the fix when OS X fixes.
,
Jan 6 2017
Thanks, I created a WebKit bug: https://bugs.webkit.org/show_bug.cgi?id=166757
,
Jan 9 2017
Thank you!
,
Jan 10 2017
Also reported at bugreport.apple.com, ID 29944454. |
||||||||||||||||
►
Sign in to add a comment |
||||||||||||||||
Comment 1 by e...@chromium.org
, Jan 2 2017Status: Assigned (was: Unconfirmed)