RESOLVED CONFIGURATION CHANGED 158771
element boundaries suppress line break opportunity 
https://bugs.webkit.org/show_bug.cgi?id=158771
Summary element boundaries suppress line break opportunity
Florian Rivoal
Reported 2016-06-14 19:06:34 PDT
I've attached a example where Safari suppresses break opportunities at element boundaries. A span with no styles attached should never affect the layout, but here it does. This bug occurs much more often in Japanese or Chinese than in English, since these languages do no use spaces as word separators, and therefore it is common to have, as in this example, a <span> (or an <em>, or a <strong>...) not surrounded with spaces. It appears that some variants of this bug have already been addressed in the past, but as this test case shows, some issues remain.
Attachments
test case showing the problem (279 bytes, text/html)
2016-06-14 19:07 PDT, Florian Rivoal 		no flags
Details
Screenshot of the issue in Safari 9.11 (11601.6.17) on OS X 10.11.5 (20.84 KB, image/png)
2016-06-14 19:08 PDT, Florian Rivoal 		no flags
Details
Safari 15.5 matches other browsers (1.22 MB, image/png)
2022-07-01 10:30 PDT, Ahmad Saleem 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Florian Rivoal
Comment 1 2016-06-14 19:07:10 PDT
Created attachment 281313 [details] test case showing the problem
Florian Rivoal
Comment 2 2016-06-14 19:08:17 PDT
Created attachment 281314 [details] Screenshot of the issue in Safari 9.11 (11601.6.17) on OS X 10.11.5
zalan
Comment 3 2016-06-14 21:07:38 PDT
Work as expected in FF 47.0, fails with Chrome 51.0.2704.84
Florian Rivoal
Comment 4 2016-06-14 21:30:55 PDT
While we're at comparing with other browsers, this works in IE, Edge and Presto as well. It's just the webkit (and derived, so blink too) browsers that have an issue with that. For chrome it's tracked here: https://bugs.chromium.org/p/chromium/issues/detail?id=282134
Ahmad Saleem
Comment 5 2022-07-01 10:30:16 PDT
Created attachment 460616 [details] Safari 15.5 matches other browsers I am unable to reproduce this bug based on attached test case and it is different from the screenshot (can be compared with attached one). It is matching with all other browsers (Chrome and Firefox) as well. I think it was fixed along the way and can the marked as "RESOLVED CONFIGURATION CHANGED". Thanks!
Ryosuke Niwa
Comment 6 2022-07-01 10:39:09 PDT
Nice!
Myles C. Maxfield
Comment 7 2022-07-05 21:41:16 PDT
🆒
zalan
Comment 8 2022-07-06 08:36:35 PDT
This is an IFC progression and we may still run into this issue as long as the legacy line layout is around (e.g. setting certain CSS properties on the block container).
Note You need to log in before you can comment on or make changes to this bug.