-
Notifications
You must be signed in to change notification settings - Fork 12
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
UX: Responsive design #115
Comments
One place where CK should really re-think things in terms of how they are responsive is in the button groups in the editor. Try making an editor with 3 or 4 button groups in CK4 and have a look at how it wraps on a phone. It's pretty ugly. You get big gaps of wasted space on the right. I would argue that button groups should be dispensed with entirely. In their place you could simply allow admins to place a divider if they like. That way every individual button can wrap to the next line and you get far less wasted space. The only caveat to this would be that there would need to be logic that keeps the divider with the icon that precedes it so that you don't get an orphan divider. |
I'd definitely vote for a touch and responsive friendly UI as we are seeing more and more users control or edit content on mobile devices (via django CMS). We faced several problems adapting CKEditor to work nicely on mobile /cc @vxsx . One of our main concerns was the overuse of iframes for displaying dropdowns and additional modals (like editing a link) |
Cleaning up old discussions. See #186. |
Does CKEditor 5 need responsive UI?
Note: This issue is not solely dedicated CKEditor 5 on mobile. It's about general usage of RWD in the UI.
Small mobile devices
Big touch devices (desktop resolution, but touch interface i.e. iPad)
Dekstop
Meta
<meta name="viewport" ...>
withwith
and*-scale
defined?The text was updated successfully, but these errors were encountered: