- From: Mats Palmgren via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Oct 2021 16:43:01 +0000
- To: public-css-archive@w3.org
That seems like a completely artificial testcase. During my 20+ years of working on Gecko I have never once seen anyone dynamically changing a `counter-increment` value as you suggest. Yes, treating zero-valued `counter-increment` differently is "inconsistent", that's the whole point of my proposal in this issue. I'm saying that doing that has practical benefits on real world web pages. Your "possibly defeating some optimization" claim is nonsense. You suggest optimizing a completely theoretical case that will never happen in practice while at the same time de-optimizing content that *we know* happen quite often on real web pages. Here's [the most recent example](https://www.planalto.gov.br/ccivil_03/constituicao/constituicao.htm) we encountered - it's a large legal document with many thousands of `<summary>` elements which are all in the same (implied) counter scope. Excluding those from our internal CSS counter data structures is a significant performance optimization in Gecko (as I was alluding to in my point 3 above). -- GitHub Notification of comment by MatsPalmgren Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6738#issuecomment-954018413 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 28 October 2021 16:43:02 UTC