-
Notifications
You must be signed in to change notification settings - Fork 792
[css-text-3] line breaks and ideographic space #2500
Copy link
Copy link
Closed
Labels
Commenter Response PendingTestedMemory aid - issue has WPT testsMemory aid - issue has WPT testsTracked in DoCcss-text-3Current WorkCurrent Worki18n-clreqChinese language enablementChinese language enablementi18n-jlreqJapanese language enablementJapanese language enablementi18n-trackerGroup bringing to attention of Internationalization, or tracked by i18n but not needing response.Group bringing to attention of Internationalization, or tracked by i18n but not needing response.
Metadata
Metadata
Assignees
Labels
Commenter Response PendingTestedMemory aid - issue has WPT testsMemory aid - issue has WPT testsTracked in DoCcss-text-3Current WorkCurrent Worki18n-clreqChinese language enablementChinese language enablementi18n-jlreqJapanese language enablementJapanese language enablementi18n-trackerGroup bringing to attention of Internationalization, or tracked by i18n but not needing response.Group bringing to attention of Internationalization, or tracked by i18n but not needing response.
Type
Fields
Give feedbackNo fields configured for issues without a type.
(reference: https://bugzilla.mozilla.org/show_bug.cgi?id=1450228)
Browsers differ in how they handle line breaks for IDEOGRAPHIC SPACE (U+3000):
try it here
Quoting @MurakamiShinyu
That logic would favor Edge's behavior.
UAX-14 says that IDEOGRAPHIC SPACE (U+3000) has class BA (for break after), which would support the behavior of Chrome/Safari/Edge over Firefox's, but:
Should we reference the BA class somehow?
Should we directly list DEOGRAPHIC SPACE (U+3000) in some level of line-break?
Should we say something about allowing/requiring it to hang?