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
Is your feature request related to a problem or unsupported use case? Please describe.
Currently when we are selecting multiple blocks we don't have access to the action menu/editor.
Example below:
with only one block selected:
with two blocks selected:
Besides some basic keyboards shortcuts are not working.
For example when selecting a bullet list and pressing "Tab" the list is not indenting. We need to indent each line manually.
Describe the solution you'd like
Have the same behaviour for one or multiple blocks. I don't see any issue related to that.
Describe alternatives you've considered
Currently we have to deal with each block individually, which is fastidious.
Discovery, Documentation, Adoption, Migration Strategy
This is a common feature amongst many docs editor so it should be pretty straightforward. Actually it is more counterintuitive as it is today.
Do you want to work on it through a Pull Request?
No.
The text was updated successfully, but these errors were encountered:
Feature Request
Is your feature request related to a problem or unsupported use case? Please describe.
Currently when we are selecting multiple blocks we don't have access to the action menu/editor.
Example below:
Besides some basic keyboards shortcuts are not working.
For example when selecting a bullet list and pressing "Tab" the list is not indenting. We need to indent each line manually.
Describe the solution you'd like
Have the same behaviour for one or multiple blocks. I don't see any issue related to that.
Describe alternatives you've considered
Currently we have to deal with each block individually, which is fastidious.
Discovery, Documentation, Adoption, Migration Strategy
This is a common feature amongst many docs editor so it should be pretty straightforward. Actually it is more counterintuitive as it is today.
Do you want to work on it through a Pull Request?
No.
The text was updated successfully, but these errors were encountered: