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? Please describe.
the other day when using the search in Collectives, with the last 2 characters it somehow switched to editing the current page (was the main page) and typed it in there instead.
It was possibly cause the collective was not completely loaded yet. So when the page was loaded it took the focus away from the search entry.
Describe the solution you'd like
When you start Collectives in edit mode, it’s fine if you have to click inside the content first. When you click on "Edit", then autofocus is expected
Describe alternatives you've considered
I think detecting situations where the focus is in a different text entry and not stealing focus then would be difficult as tiptap simply has an autofocus parameter that we set when starting to load the editor.
Additional context
First reported by @jancborchardt in office public chat.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
the other day when using the search in Collectives, with the last 2 characters it somehow switched to editing the current page (was the main page) and typed it in there instead.
It was possibly cause the collective was not completely loaded yet. So when the page was loaded it took the focus away from the search entry.
Describe the solution you'd like
When you start Collectives in edit mode, it’s fine if you have to click inside the content first. When you click on "Edit", then autofocus is expected
Describe alternatives you've considered
I think detecting situations where the focus is in a different text entry and not stealing focus then would be difficult as tiptap simply has an autofocus parameter that we set when starting to load the editor.
Additional context
First reported by @jancborchardt in office public chat.
The text was updated successfully, but these errors were encountered: