Open
Bug 1448776
Opened 7 years ago
Updated 9 months ago
Allow line-break after - (U+002D / hyphen-minus) between digits.
Categories
(Core :: Layout: Text and Fonts, enhancement, P4)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox61 | --- | affected |
People
(Reporter: karlcow, Unassigned)
References
()
Details
(Whiteboard: [text])
Attachments
(1 file)
27.59 KB,
image/png
|
Details |
This is a spin-off of a webcompat issue https://webcompat.com/issues/6603
Firefox will not break after the hyphen-minus while Chrome and Safari do.
test case here
https://codepen.io/webcompat/pen/YareqB
Reporter | ||
Updated•7 years ago
|
See Also: → https://webcompat.com/issues/6603
Comment 1•7 years ago
|
||
[Original bug title was misleading: the example shown has the hyphen-minus between two digits, not "immediately followed by a letter".]
Currently, Gecko deliberately does not break in a sequence <digit, hyphen-minus, digit>:
https://searchfox.org/mozilla-central/rev/003262ae12ce937950ffb8d3b0fa520d1cc38bff/intl/lwbrk/LineBreaker.cpp#793-794
Changing this could have pretty widespread implications; it's not immediately clear to me whether on balance it would be an improvement or not.
Summary: Allow line-break after - (U+002D / hyphen-minus) when immediately followed by letter. → Allow line-break after - (U+002D / hyphen-minus) between digits.
Reporter | ||
Comment 2•7 years ago
|
||
Jonathan, yup.
Reporting for recording the difference, not necessary to create a change in the meantime, and given this is one site only I don't think it is a priority.
Thanks for fixing the title.
Updated•7 years ago
|
Priority: -- → P4
Reporter | ||
Updated•6 years ago
|
See Also: → https://webcompat.com/issues/25176
Comment 3•6 years ago
|
||
Migrating Webcompat whiteboard priorities to project flags. See bug 1547409.
Webcompat Priority: --- → ?
Comment 4•6 years ago
|
||
See bug 1547409. Migrating whiteboard priority tags to program flags.
Reporter | ||
Updated•5 years ago
|
See Also: → https://webcompat.com/issues/40415
Updated•5 years ago
|
Webcompat Priority: ? → ---
Updated•2 years ago
|
Severity: normal → S3
Comment 6•9 months ago
|
||
The layouts of the websites hitting this issue have changed, and no longer seem to have the issue. Let's drop the webcompat flag for now.
Whiteboard: [webcompat] [text] → [text]
You need to log in
before you can comment on or make changes to this bug.
Description
•