Open Bug 2018384 Opened 8 months ago Updated 6 months ago

Do not injecting extra space surrounding Hangul characters

Categories

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

Firefox 147
defect

Tracking

()

People

(Reporter: shanshandehongxing, Unassigned)

References

Details

User Agent:
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:147.0) Gecko/20100101 Firefox/147.0
Firefox for Android

Steps to reproduce:

  1. Open https://www.zhihu.com/question/351035750/answer/3568725796

Actual results:

Some extra spacing can be seen in "新國旗의制定과太極旗의廢止에對하여", although there's no spaces in it if you open developer tool to see.

Expected results:

Firefox shouldn't inject spacing between Hangul, Hanja, and so on.

The Bugbug bot thinks this bug should belong to the 'Firefox for Android::General' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → General
Product: Firefox → Firefox for Android

I've already reproduced on Windows 10 while I report, so revert last change that was made by bot.

Product: Firefox for Android → Firefox

Not sure if it should be Graphic::Text or Layout::Font, but moving so people with more knowledge about font rendering can have a look. Looks like Safari is also inserting spaces while Chrome is not.

Component: General → Graphics: Text
Product: Firefox → Core

This is the result of text-autospace: normal, which encompasses the ideograph-alpha value. We should double-check the definitions of the character classes involved there to confirm the expected behavior.

Component: Graphics: Text → Layout: Text and Fonts

I think Google Chrome may have already implemented this CSSWG resolution to use Unicode East Asian Auto Spacing for text-autospace, which has more granular control than what is defined in the current CSS Text spec.

https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/layout/inline/text_auto_space.cc

Blocks: 1869577
Severity: -- → S3
Status: UNCONFIRMED → NEW
Ever confirmed: true

(In reply to Jonathan Kew [:jfkthame] from comment #5)

We should double-check the definitions of the character classes involved there to confirm the expected behavior.

I've shown some materials for this in comment 1, in which you'll see the discussion from another community, and you'll found some historical resources to see what Koreans did.

You need to log in before you can comment on or make changes to this bug.