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)

61 Branch
Unspecified
All
enhancement

Tracking

()

Tracking Status
firefox61 --- affected

People

(Reporter: karlcow, Unassigned)

References

()

Details

(Whiteboard: [text])

Attachments

(1 file)

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
[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.
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.
Priority: -- → P4

Migrating Webcompat whiteboard priorities to project flags. See bug 1547409.

Webcompat Priority: --- → ?

See bug 1547409. Migrating whiteboard priority tags to program flags.

Severity: normal → S3

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.

Attachment

General

Created:
Updated:
Size: