HTML Ordered list's numbering is restarted if the content splits on multiple pages

Progress® Telerik® Reporting Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Planned

Last Updated: 12 Mar 2026 21:14 by Simon

Dimitar

Created on: 21 May 2021 10:17

Category: Reporting

Type: Bug Report

HTML Ordered list's numbering is restarted if the content splits on multiple pages

DOCX export restarts the numbering on the second page for ordered lists.

3 comments

Simon

Posted on: 12 Mar 2026 21:14

Hi guys,

In February 2023, Ivan confirmed this as a bug and indicated it would be addressed in the R2 2023 release. That was three years ago. The bug is still present.

I want to be respectful of the work your team does, but I also need to be direct: a public commitment to fix a bug in a specific release, followed by three years of silence, is not acceptable. We have been waiting on this since May 2021 - nearly five years in total.

The practical impact on our end has not diminished. We generate compliance and governance reports for local government clients where numbered lists carry legal significance. A list that silently restarts at (1) on a new page produces a document that misrepresents its own content. We cannot hand that to a client.

To compound the problem, the PDF renderer has a related defect where an HtmlTextBox containing a long list splits mid-line at a page boundary rather than at a text line boundary (separate ticket submitted). Between the two issues, HtmlTextBox list content cannot be rendered correctly across page boundaries in either of your two primary export formats.

Could you please provide a concrete update: is this still scheduled for a future release, and if so, which one? If it has been deprioritised or closed, please say so plainly so we can make an informed decision about our rendering approach going forward.

Thank you.

Simon

ADMIN

Ivan Hristov

Posted on: 17 Feb 2023 10:47

Hi Simon,

Thank you for bringing this issue to our attention.

You're completely right - we recognize this as a bug and the vote count doesn't have as much weight as with the feature requests. We have discussed the bug internally and we believe we'll be able to squeeze it in for implementation for our R2 release.

You should receive automated notification about each change of the status of the public feedback item.

Regards,
Ivan Hristov
Progress Telerik

Simon

Posted on: 13 Feb 2023 01:12

Hi guys,

21 months have passed and this bug remains unplanned. I can understand if it were a feature request, but this is a bug. I hope your not waiting for more votes to provide the impetus to fix a bug. it may be that only one of your clients has brought this to your attention, but we have several clients that have brought this to our attention. A bug needs to be fixed.

Can you please provide an update on this?

Looking forward to hearing from you.

Thanks, Simon