RESOLVED INVALID 56018
Soft hyphen can cause unnecessary line wrap 
https://bugs.webkit.org/show_bug.cgi?id=56018
Summary Soft hyphen can cause unnecessary line wrap
David Sosby
Reported 2011-03-09 08:22:02 PST
Created attachment 85180 [details] Demonstration of issue Sometimes when a line break occurs on a soft hyphen, the next line is broken after the first word producing 3 lines when there should only be 2. This was seen while testing Bug 56017. This behavior has been observed on Chrome 9.0.597.107 534.13 (Windows and Ubuntu10.10), WebKitGTK 534.21+, and Windows Safari 5.0.3 (7533.19.4). Demonstration of issue attached.
Attachments
Demonstration of issue (672 bytes, text/html)
2011-03-09 08:22 PST, David Sosby 		no flags
Details
Screenshot of the issue (28.37 KB, image/png)
2011-03-09 09:24 PST, David Sosby 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
mitz
Comment 1 2011-03-09 08:35:25 PST
Can you attach a screenshot? I don’t seem to be able to reproduce the bug as described.
David Sosby
Comment 2 2011-03-09 09:24:19 PST
Created attachment 85184 [details] Screenshot of the issue Note that the hyphen appears in this screenshot as I have a proposed patch for bug 56017 installed. Without this fix the hyphen would not be displayed though the line breaks still occur as seen.
David Sosby
Comment 3 2011-03-09 09:25:33 PST
This issue was seen w/o the proposed 56017 fix as well.
mitz
Comment 4 2011-03-09 10:25:48 PST
Which is the unexpected line break? I see three, all accounted for: after “anti”, a soft line break at the soft hyphen; after “aliasing”, a hard line break due to the <br> element; after “new”, a soft line break at a space.
David Sosby
Comment 5 2011-03-09 10:31:19 PST
(In reply to comment #4) > Which is the unexpected line break? I see three, all accounted for: after “anti”, a soft line break at the soft hyphen; after “aliasing”, a hard line break due to the <br> element; after “new”, a soft line break at a space. Agreed, this is not a bug. Mistake on my part and should be closed.
Note You need to log in before you can comment on or make changes to this bug.