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
Hi, the formatting buttons across the top in the editor are not accessible in a mobile browser in portrait mode, you have to rotate to landscape for them to appear.
Same when you shrink the PC web browser window too small.
Can a button be added to reveal these "Colapsed" buttons when the page size is reduced?
The text was updated successfully, but these errors were encountered:
My expectiation was not that people really edit on their mobile devices. I assumed that this would only be for quick fixes. With the keyboard covering a large part of your screen, I would not want a bunch of buttons to steal even more space.
I will check how I can add buttons on mobile. Design ideas or Pull requests are welcome.
Well, my post was from trying out the demo, but I've now transferred my home lab Docuwiki over to OtterWiki & loving it!
I haven't used markdown before but I easily remember most of the markdown symbols to not need the buttons, especially that the popup markdown help chart can be opened at the bottom of the editor window. :-D
A lot of the time, I'll lookup things on my mobile but never document them because Docuwiki is too clunky on mobile but OtterWiki works great.
One feature request would be, on the create new page screen, add a drop down box that contains a list of all current pages & subdirectories which can be selected to create a new subdirectory under, instead of having to write out "parentpage/subpage/subsubpage".
Hi, the formatting buttons across the top in the editor are not accessible in a mobile browser in portrait mode, you have to rotate to landscape for them to appear.
Same when you shrink the PC web browser window too small.
Can a button be added to reveal these "Colapsed" buttons when the page size is reduced?
The text was updated successfully, but these errors were encountered: