Open Bug 1645314 Opened 2 years ago Updated 2 months ago

Line breaking opportunities in Japanese are different in firefox and chrome

Categories

(Core :: Layout: Text and Fonts, defect)

75 Branch
Unspecified
Android
defect

Tracking

()

Webcompat Priority P3
Tracking Status
firefox79 --- affected

People

(Reporter: karlcow, Unassigned)

References

()

Details

  1. go to https://www.maruzenjunkudo.co.jp/info/20200409-01/

Notice the broken renderin in Firefox Android. Compare to chrome.

Ksenia has created a test case.
https://codepen.io/ksy36/pen/PoPRZxP

We can see that Chrome is breaking at different places. indeed.

On the original site.

<a href="https://honto.jp/store/detail_1570046_14HB320.html" target="_blank" rel="noopener noreferrer">MARUZEN&ジュンク堂書店 札幌店</a>

For example, in between N (LATIN CAPITAL LETTER N) and (FULLWIDTH AMPERSAND != AMPERSAND)

for 11:00~19:00 we get a DIGIT ZERO and FULLWIDTH TILDE and DIGIT ONE which chrome is breaking and not firefox.

In general, it's not guaranteed (or even expected) that browsers will always agree on line breaks; there's no single "correct" behavior, and various heuristics may come into play.

:m_kato might have some opinion on the specific examples here.

Severity: -- → S4
Flags: needinfo?(m_kato)

<a href="https://honto.jp/store/detail_1570046_14HB320.html" target="_blank" rel="noopener noreferrer">MARUZEN&ジュンク堂書店 札幌店</a>

No, I think that this is another point. This issue is break rule of 10:30~19:00(月~木). As long as UAX14 rule is NU ÷ East Asia OP, this Gecko rule is different of UAX14.

Flags: needinfo?(m_kato)

Our current break rule test is considering historical issue of supporting ASCII face mark, so I don't have good decision for all. (At least, I think that this issue is comment #2)...

Setting webcompat P3 priority for now, as we've only seen one such piece of breakage in two years, and doesn't seem to be a major site or major breakage.

Webcompat Priority: ? → P3
You need to log in before you can comment on or make changes to this bug.