Skip to content

list keyboard shortcut other than "1" #1299

New issue

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

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

Already on GitHub? # to your account

Closed
YousefED opened this issue Dec 3, 2024 · 0 comments · Fixed by #1326
Closed

list keyboard shortcut other than "1" #1299

YousefED opened this issue Dec 3, 2024 · 0 comments · Fixed by #1326
Labels
enhancement New feature or request

Comments

@YousefED
Copy link
Collaborator

YousefED commented Dec 3, 2024

When you add an indented table in an ordered list, the list won’t continue ordering.

See video:

Kapture.2024-11-07.at.10.16.22.mp4

The same issue can be recreated without a table:

  • create a list item
  • hit enter to create a second list item, remove it (backspace)
  • now, a new list item can only be created by typing “1. “, but the user probable expects it to be created by typing “2. ”

I think there are 3 ways to fix it.

First of all, we need to be able to create a list item when any number is entered, not just 1. . This should already fix the issue above. But then, we have the question what should happen when you enter 2. when you're not in a list (for example, you type 2. in an empty document). Couple of options:

a) trigger regular “list-creation” always on typing “. “, regardless of cursor position. This will have a bit weird behaviour because when you’d start a new list with “2. “, it will change it into “1. ” (as it creates a new list that starts as 1)
b) option (a), but the new list would start at “2.” this would require a list-start attribute of some sorts to be added. I think this is the approach notion has.
c) Only make typing “2. ” work when we’re typing it at the correct position (i.e. after a single list item). This is more inline with MS Word

Imo, let's go for option (b) as it's most inline with Notion

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant