CSS counter-increment Property issue on dynamic page item lists
Reported by
givito...@googlemail.com,
Mar 22 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: 1. Open a questionnaire 2. Click on answer to trigger child question 3. CSS counter-increment changes all page numbering to that of the child when on initial page load all numbering was correct. What is the expected behavior? It is a questionnaire which dynamically expands or contracts based on user answers. On page load the numbering is correct for all questions at any level. When a child question is triggered, the numbering on all questions is changed to reflect the number of that child question. This is not correct behavior. What went wrong? Normally numbering is 1.1, 1.1.1, 2.1, etc. Now in this update of Chrome numbering will go 1.1, 1.1.1, 1.1.2 removing the 2.1 number and replacing with the next child numbing format so 1.1.2. Did this work before? Yes The previous Chrome build Does this work in other browsers? Yes Chrome version: 65.0.3325.181 Channel: stable OS Version: 10.0 Flash Version: The numbering continues to work without issue in Firefox, IE, Edge, Opera, Safari but now Chrome no longer functions properly. Our web app has been using this CSS property with no issues for well over 2 years now.
,
Mar 23 2018
givitoomi@ Thanks for the issue. Request you to provide the URL where this issue can be reproduced, which will help in further triaging. Thanks..
,
Mar 23 2018
Unfortunately our web app is not open to public users. I will try and figure out a way to display this issue, maybe in a fiddle sample.
,
Mar 23 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 23 2018
,
Mar 26 2018
givitoomi@ Thanks for the feedback. As per comment #3, adding 'Needs-Feedback' label as the reporter will provide a JSfiddle where the issue can be reproduced, which will help in further triaging. Thanks..
,
May 2 2018
I just run into the same issue, here a reproduction I extracted from our app: https://jsfiddle.net/s4bL8gqs/1/
,
Jun 24 2018
Looks like it works correctly on the current Chrome Canary on Mac: Version 69.0.3469.2 (Official Build) canary (64-bit) |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by susan.boorgula@chromium.org
, Mar 23 2018