Nested Ordered List issue when assigning values to counter
See original GitHub issueI’ve come across an issue when using html-to-pdfmake.
When I create an ordered list within an ordered list and using values that update the counter - the list item containing the nested ordered list does not update the counter that is included in the HTML.
For example :
<ol>
<li data-pdfmake="{"counter":7}">One</li>
<li data-pdfmake="{"counter":8}">Two
<ol>
<li data-pdfmake="{"counter":6}">Three</li>
</ol>
</li>
<li data-pdfmake="{"counter":7}">Four</li>
</ol>
Shows up as : 7.One 2.Two -> nested 6.Three 7.Four
Issue Analytics
- State:
- Created a year ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
HTML ordered list 1.1, 1.2 (Nested counters and scope) not ...
With this, the html parser sees all li as the list item and assign the appropriate value to it, and sees the ol,...
Read more >Nested Ordered lists causes the parent li not to change ...
It tries to change the text counter but it ignores any value or counter being changed in text object. ... Actual result ,...
Read more >How to Display an Ordered List with Nested Counters - W3docs
In this snippet, we're going to show how you can display an ordered list with nested counters by using CSS. See some methods...
Read more >Nested ordered lists with counters, driving me nuts! - SitePoint
I have been struggling with creating a nested ordered list, numbered correctly with decimals, using CSS 2.1 counters. To appear like so:.
Read more >1696201 - List numbering fails to ignore nested lists
The Bugbug bot thinks this bug should belong to the 'Core::Layout: Generated Content, Lists, and Counters' component, and is moving the bug to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The new version (v2.3.11) should solve this issue.
Interesting, I definitely updated to latest version but perhaps there’s something else going on. Thanks for responding so fast