Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto continuity of a subsequent ordered list #38251

Open
ghost opened this issue Jan 26, 2022 · 6 comments
Open

Auto continuity of a subsequent ordered list #38251

ghost opened this issue Jan 26, 2022 · 6 comments
Labels
[Block] List Affects the List Block [Priority] Low Used to indicate that the issue at hand isn't a top priority to address and can be handled later [Type] Enhancement A suggestion for improvement.

Comments

@ghost
Copy link

ghost commented Jan 26, 2022

What problem does this address?

When we need to break the list into separate lists for any reason (like adding a table or image or note), the starting number of the subsequent list is not automatically incremented or decremented.

What is your proposed solution?

We need an option by which the subsequent list block should be auto-incremented or decremented based on the list items changed in the previous list block. Similar to the "continue numbering" option in Word.

For example:

  1. List Item 1
  2. List Item 2

(Break List)

  1. List Item 3 (Currently, this number requires to be manually adjusted inside the Ordered List Settings option. This number should be automatically adjusted according to the changes in the above list.)
  2. List Item 4
@annezazu
Copy link
Contributor

annezazu commented Feb 9, 2022

Hey there! I agree. I think this issue might be a duplicate though of this earlier one: #6394 Do you agree? If so, I can close this out :)

@annezazu annezazu added the [Block] List Affects the List Block label Feb 9, 2022
@ellatrix
Copy link
Member

@annezazu Nothing to do with nested blocks.

For now you'll need to manually change the start number of the list unfortunately. No plans to automatically update it based on a previous list, unless there's someone who wants to work on that.

@annezazu annezazu added the [Type] Enhancement A suggestion for improvement. label Jul 26, 2022
@annezazu
Copy link
Contributor

Got it! Let's leave this open as now in that case.

@ghost
Copy link
Author

ghost commented Jul 27, 2022 via email

@oliv-j
Copy link

oliv-j commented Nov 12, 2022

I will add to this that manually specifying the start attribute of the list item breaks the editor when you try to go back to visual editing. So there is no good work around right now. I get:
"This block contains unexpected or invalid content."

If I attempt recovery then all hell breaks loose with duplicated content and/or list items with strange line breaks in between them.
I've been trying to get round this for 30 minutes but each time I end up ctrl-z'ing like crazy to try and get the list back to how it was.

For the moment I've implemented a CSS change to hide the first level ordered list items' numbers and then written the numbers in by hand.

For background context: I have a number of pages which are laid out as legal documents and they often require a table or other content in between list items.

@ellatrix
Copy link
Member

So you want to keep the numbering when you split a let in two, is that correct?

We can adjust the number on split, but the problem is that this "start" number doesn't update when you add items to the first list. Automatically updating the start number is very difficult, because we need to know which list the count is based off, so that means keeping track of the previous list. I'm afraid this is beyond what we can do in core, but I'm not opposed to it if someone wants to try it in a PR.

A better solution might be allowing other blocks to be added to the list? #17999

@ellatrix ellatrix added the [Priority] Low Used to indicate that the issue at hand isn't a top priority to address and can be handled later label Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Block] List Affects the List Block [Priority] Low Used to indicate that the issue at hand isn't a top priority to address and can be handled later [Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

No branches or pull requests

3 participants