You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 Adlam, this means that the decimal numeric list style that uses Adlam digits cannot be used for CSS-styled counters.
Priority:
Adlam digits are used for counters in documents, and so should be available via CSS. Therefore, this is marked as a basic issue.
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.
The text was updated successfully, but these errors were encountered:
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.
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 Adlam, this means that the decimal numeric list style that uses Adlam digits cannot be used for CSS-styled counters.
More:
Priority:
Adlam digits are used for counters in documents, and so should be available via CSS. Therefore, this is marked as a basic issue.
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.
The text was updated successfully, but these errors were encountered: