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
I'm pretty sure prior to Umbraco v8, the rich text editor fields were independently scrollable, however in v8 I think this has been updated so that the input resizes based on the content within it. This is cool, but now if you create a lot of rich text content the editor toolbar goes off page and can be a pain to relocate. I know there is a new "distraction free" mode, but I'm not a fan of that approach as it can be buggy to get the toolbar to show when you need it.
A nice, simple alternative could be to just make the RTE toolbar sticky such that when you scroll the main editor window, the rte toolbar remains stuck just below the main menu bar. If you were to scroll beyond the RTE area, you could then just let it disapear and only re-appear when the RTE comes back into view.
I think this would be a much nicer UX and means the RTE toolbar is never out of reach.
The text was updated successfully, but these errors were encountered:
I'm pretty sure prior to Umbraco v8, the rich text editor fields were independently scrollable, however in v8 I think this has been updated so that the input resizes based on the content within it. This is cool, but now if you create a lot of rich text content the editor toolbar goes off page and can be a pain to relocate. I know there is a new "distraction free" mode, but I'm not a fan of that approach as it can be buggy to get the toolbar to show when you need it.
A nice, simple alternative could be to just make the RTE toolbar sticky such that when you scroll the main editor window, the rte toolbar remains stuck just below the main menu bar. If you were to scroll beyond the RTE area, you could then just let it disapear and only re-appear when the RTE comes back into view.
I think this would be a much nicer UX and means the RTE toolbar is never out of reach.
The text was updated successfully, but these errors were encountered: