You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
V2 now uses ordered lists for all list types (https://quilljs.com/docs/upgrading-to-2-0#parchment). If you want an ordered list ensure the list items have the attribute data-list="ordered" and for unordered lists, ensure list items have the attribute data-list="bullet". For example:
<!-- ordered list --><ol><lidata-list="ordered">1</li><lidata-list="ordered">2</li><lidata-list="ordered">3</li></ol><!-- unordered list --><ol><lidata-list="bullet">a</li><lidata-list="bullet">b</li><lidata-list="bullet">c</li></ol>
I understand that. I'm asking why this doesn't allow for backfitting existing solutions. I have tables with thousands and thousands of records. You're saying I have to go carefully modify the html in every record? That's not a viable solution.
Ah so if you feed your HTML using the clipboard convert function it should transform your semantic HTML (<ul>,<ol>) into quill's <ol> lists. For example:
Implementing on an existing application with old entries, we have many with
<ul>
elements. These entries are not displaying in the editor.HTML:
Testing text before tag\n<ul>\n<li>Here is older entry\n<li>Bullet 2\n<li>Bullet 3\n</ul>
Rendered:
Edit Form:
If I manually change the HTML and replace
<ul>
with<ol>
, the edit form will show the textHTML (mod):
Testing text before tag\n<ol>\n<li>Here is older entry\n<li>Bullet 2\n<li>Bullet 3\n</ol>
Edit Form (mod):
The text was updated successfully, but these errors were encountered: