Summary: | No line break opportunity between a slash and a latin character, in contradiction to the Unicode standard | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | mitz | ||||||
Component: | Text | Assignee: | Nobody <webkit-unassigned> | ||||||
Status: | NEW --- | ||||||||
Severity: | Normal | CC: | ap, jfernandez | ||||||
Priority: | P2 | Keywords: | InRadar | ||||||
Version: | 528+ (Nightly build) | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Bug Depends on: | 195345, 181169 | ||||||||
Bug Blocks: | |||||||||
Attachments: |
|
Description
mitz
2012-04-13 12:56:12 PDT
Mitz also mentioned to me that a potential downside is that we'll wrap strings like "km/h", which can be particularly bad in table titles. I think this bug could be solved once we implement line-break; anywhere and overflow-wrap: anywhere As a matter of fact, I'm not sure whether this bug should be marked as FIXED. There are indeed breaking opportunities between a slash and a latin character by using the 'word-break: break-all' feature. Attached a test case and the rendering result using trunk (r244730) Created attachment 368590 [details]
Test case to reproduce the issue
Created attachment 368591 [details]
Actual result
|