Open r12a opened 4 years ago
The first comment in this issue contains text that will automatically appear in one or more gap-analysis documents as a subsection with the same title as this issue. Any edits made to that comment will be immediately available in the Editor's draft of the document. Proposals for changes or discussion of the content can be made by following the link to the GitHub issue being used to track this gap and adding comments there.
If a counter style is supported but with the wrong separator, that should be filed as a separate issue against the implementations...
Added links to the i18n test suite.
Customisable counters are needed for many languages.
There is no way for users to create local counter styles that are not built in to the browser, and users also often want to tweak the counter style in some way (esp. the prefix/suffix).
For Japanese, this means that a number of predefined counter styles in the CSS Counter Styles spec are not widely supported by browsers, or use a different separator from that specified. Because the custom mechanism of the Counter Styles spec is not supported by browsers other than Firefox, users are unable to fix this for themselves.
The following are additional items of Japanese-specific information.
Tests & results: i18n test suite, Basic tests for support of @counter-styles i18n test suite, Tests for hiragana/katakana styles i18n test suite, Tests for kanji character styles
Browser bug reports:
Chromium WebKit
FIXED !
This gap is now fixed. For more details, see this GitHub issue, which is being used to track this gap. Please add any discussion there, and not to this issue.