-
Notifications
You must be signed in to change notification settings - Fork 22.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with "counter-reset": What is the difference in behavior between the latest Firefox (82 or later) and the older 81 or earlier or other browsers? #13293
Comments
I have rewritten Using CSS counters. That draft document is https://css-counters.lavoscore.org/. My rewrite contains the following issues:
To account for these issues, Using CSS counters needs to be rewritten and linked from other related documents. |
@debiru, If you open a pull request with your changes, that could be reviewed and eventually merged. We don’t otherwise have a process for reviewing changes posted elsewhere. |
I have not expect you to review drafts written on external sites. It is written only for reference. As indicated in this topic, the behavior regarding counter-reset has changed after Firefox 82, and users cannot learn more about those behaviors just by reading MDN. This Issue seeks to remedy that situation. However, I am not able to make a complete pull request including https://github.com/mdn/browser-compat-data/. I will put it on hold for the time being. |
I've raised a Chromium bug because it doesn't respect the inbuilt |
MDN URL: https://developer.mozilla.org/en-US/docs/Web/CSS/counter-reset
Maybe the page to fix is this: https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Counter_Styles/Using_CSS_counters
What information was incorrect, unhelpful, or incomplete?
It is my hope that the documentation will clearly explain why each browser behaves the way it does.
In particular, I think the following current statement is wrong.
The latest version of Firefox doesn't seem to reset to on each occurrence of the element. This may just be because it resets the counter, but creates another instance, which makes it look like the counter is not being reset.
Related specs
Related links
What did you expect to see?
I don't know what the specs say about subtle nuances and what is the right way to behave.
MDN Content page report details
en-us/web/css/counter-reset
The text was updated successfully, but these errors were encountered: