-
-
Notifications
You must be signed in to change notification settings - Fork 315
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
Serious mobile view problems - near 0 editing space #368
Comments
Hi, @vanillamasonry
Thank you. |
Dear Lee, First of all I want to thank you for your fast reply, taking in consideration my suggestion and clarifying the Focus issue. On the hand I have setup the editor in one application and after Beautifying the suneditor.min.js and tracking down the error I have found that setContents: function(t) { removing ", d.history.push(!1)" from the else statement, the loading, creation editing etc... was working without any errors. I have no idea what "d.history.push(!1)" is doing and I am wondering if is OK to delete it I hope that you will have time to review also this problem for the next release. Thank you, |
The 2.30.0 version has been updated. |
The buttons and the toolbars are too big, The editor is useless for mobile apps and sites. You must find another solution. The current solution is OK for desktop and tablets
And another problem... the android selection prompt do not disappear after selection... see the red circle form screenshot.
Visiting your website 5.2 inch phone - No real space to edit
And another screenshot from a larger phone 6.7 inch
You must add an icon version for font type, font size, paragraph and use only ONE toolbar with a popup button - toolbox for the rest of buttons may be something like this:
another solution from CKEditor
or even better look at Microsoft word for mobile/desktop that combine tabs and toolbars. I think that is the best solution (elegant, professional, space saving) for mobile, desktop, and the inline editor when you want more buttons/options.
I hope that the next version will be usable for mobile apps / websites. On the other hand excepting this bug (prompt bug) and design problems ... you have done a very good job.
Thank you in advance,
Paul
The text was updated successfully, but these errors were encountered: