Skip to content
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

Closed
debiru opened this issue Feb 26, 2022 · 4 comments · Fixed by #35258
Labels
Content:CSS Cascading Style Sheets docs

Comments

@debiru
Copy link
Contributor

debiru commented Feb 26, 2022

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 value to reset the counter to on each occurrence of the element. Defaults to 0 if not specified.

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
@github-actions github-actions bot added the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Feb 26, 2022
@sideshowbarker sideshowbarker added Content:CSS Cascading Style Sheets docs and removed needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. labels Feb 26, 2022
@debiru
Copy link
Contributor Author

debiru commented Mar 3, 2022

I have rewritten Using CSS counters. That draft document is https://css-counters.lavoscore.org/.

My rewrite contains the following issues:

  • Since I am Japanese and not good at English, there is a possibility that the English sentence is incorrect.
  • Last item in browser compatibility "Does not apply implicit ..." is not an implementation item specified in the specification.
  • Other documents, such as counter-reset, have not been modified, but we have not decided how to indicate the relevant documents.

To account for these issues, Using CSS counters needs to be rewritten and linked from other related documents.

@sideshowbarker
Copy link
Member

@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.

@debiru
Copy link
Contributor Author

debiru commented Mar 3, 2022

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.

@OnkarRuikar
Copy link
Contributor

I've raised a Chromium bug because it doesn't respect the inbuilt list-item counter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content:CSS Cascading Style Sheets docs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants