WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
NEW
83934
No line break opportunity between a slash and a latin character, in contradiction to the Unicode standard
https://bugs.webkit.org/show_bug.cgi?id=83934
Summary
No line break opportunity between a slash and a latin character, in contradic...
mitz
Reported
2012-04-13 12:56:12 PDT
<
rdar://problem/11246877
> WebKit doesn’t recognize a line breaking opportunity between a slash and a latin character (e.g. after the slash in “before/after”), but the Unicode standard, specifically UAX #14, says that there is a line break opportunity there (see <
http://www.unicode.org/reports/tr14/#SY
>). The Unicode behavior allows long URLs to wrap better. See also
bug 37698
.
Attachments
Test case to reproduce the issue
(158 bytes, text/html)
2019-04-30 12:56 PDT
,
Javier Fernandez
no flags
Details
Actual result
(1.06 KB, image/png)
2019-04-30 12:58 PDT
,
Javier Fernandez
no flags
Details
View All
Add attachment
proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1
2012-04-13 13:36:38 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.
Javier Fernandez
Comment 2
2019-04-30 08:33:32 PDT
I think this bug could be solved once we implement line-break; anywhere and overflow-wrap: anywhere
Javier Fernandez
Comment 3
2019-04-30 12:54:43 PDT
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
)
Javier Fernandez
Comment 4
2019-04-30 12:56:50 PDT
Created
attachment 368590
[details]
Test case to reproduce the issue
Javier Fernandez
Comment 5
2019-04-30 12:58:16 PDT
Created
attachment 368591
[details]
Actual result
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug