Lack of support for applying extra spacing between Chinese/Japanese and Western text
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 809
- Forks
- 66
- Avg merge
- 19m
- Merged PRs (30d)
- 1
Description
This issue applies to Chinese and Japanese.
In Chinese and Japanese composition, it is usually recommended to apply extra spacing between Chinese/Japanese han/kana characters and certain other types of text to make the text read better. The gap is typically used between han/kana characters and Latin letters, numbers, or punctuation, and should be smaller than an ASCII space would be.
ASCII spaces are not only too wide, but they spoil the semantics and behaviour of the text.
More:
The GAP (original text)
Currently, browsers do not support this feature, so content authors have to work around the problem by adding spaces manually, but because this produces too wide spaces and inserts characters that are not appropriate into the text, many texts don't have any gap between these runs of text.
In the css-text specification, text-autospace is intended to create 1/8em extra spacing between runs of ideographs/kana and Western letters/numerals.
In order to remediate texts where ASCII spaces have been used, the CSS text-autospace property also has a replace value, which will (without changing the underlying code points) replace the spaces with an appropriately-sized gap during the rendering of the text.
By default space should be added (the default value is normal, which is equivalent to ideograph-alpha and ideograph-numeric.)
Gecko, Blink, and Webkit browsers all fail to add the extra spacing between runs of ideographs and non-ideographic letters.
Priority
Given that, though not ideal, people have been forced to omit the gap or (worse) use ASCII spaces, this is prioritised as an advanced issue, however this is really a basic feature of Chinese/Japanese text, and so needs to be addressed.
Tests & results
Action taken
Bug reports: Gecko 1 • Gecko 2 • Blink 1 • Blink 2 • WebKit 1 • WebKit 2 • WebKit 3
GH issues: spacing
Outcomes
As of version 18.4 WebKit browsers now support text-autospace: ideograph-alpha|ideograph-numeric, but they don't yet support the replace keyword. This is problematic because, many websites currently use a space to separate these items, even though it is not ideal.
WebKit also applies no-autospace as the default, contrary to the CSS spec, which expects the value to be normal. There is an ongoing discussion about whether the default behaviour should add or not add gaps.
Gecko is considering support but it is not yet available.
The Blink issue has been marked as fixed on Jul 10, 2025. It is not yet available on Blink browsers.
Unicode proposal: EAST ASIAN AUTO SPACING (Proposal)
| text-autospace | Blink | Gecko | WebKit |
|---|---|---|---|
| ideograph-alpha | ❌ | ❌ | ✅ |
| ideograph-numeric | ❌ | ❌ | ✅ |
| replace | ❌ | ❌ | ❌ |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the CSS Text Level 4 text-autospace specification and the linked line_paragraph_tests cases for ideograph-alpha, ideograph-numeric, and replace. Compare the reported Gecko, Blink, and WebKit status with the default-value discussion; completion depends on an agreed, updated requirement or status rather than a change in this repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- documentation, internationalization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100