-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Default skin needs polish #3697
Comments
Hello ! But we might find an in between solution, like a "+" button in the toolbar to display the hidden formatting buttons? It's just a bit more work. I'm not a mobile user, so please help me to understand the need ! |
There was an attempt to fix this issue with #3703, but I guess we need to do another try. I would be ok with putting a "+" button when the screen gets too narrow (to leave as much space as possible to the text), but other solutions could be ok, as well. One thing that we might want to ensure is that the solution works with both the legacy skin and Colibris. |
ok, trying to fix right now |
This is a clever solution, but having to use a scrollbar to access buttons won't be convenient for users. You should instead break the bar into two rows, when it doesn't fit on screen. |
Partially fixes ether#3697 Makes the toolbar more responsive.
The problem with going with 2 rows, is that if your etherpad install have a lot of fonctionalities, it will goes with 3 rows, maybe 4, and at the end you do not get the text, which the more important thing. That why I think the multi rows toolbar is not a solution If you guys think scrolling is not a good solution either, then we need to add this "+" button to display all the buttons. re your PR @pkrasicki, it's breaking the white background on colibris skin, and also some paddings. Also I made a fix to remove the left margin when the gutter is hidden Seems like we are working both on the same thing. if it's fine by you, could I handle this issue? |
Sure, go ahead. Edit: |
Quick test of #3709 with my Firefox 74. Some questions follow. This is the effect on Colibris: This is the effect on the legacy skin: @seballot, I did not have the time to test what happens with more icons. How do the toolbars get split? Do they arrange in multiple rows? Also, the commit message needs to describe what changed (referencing a Github issue is ok for quick work, but cannot end up as-is in the history). I can take care of it of it's easier for you. @pkrasicki: thanks for your proposal. Even if it did not get merged, your effort was useful to bring up the discussion and reach a better solution overall. Probably we would not have had anything wasn't for your initiative. Thanks again. |
Hi @muxator ! ok for the commit message, sorry :) When more icons, see my screencast on #3697 (comment) As @pkrasicki mentioned that the scrolling toolbar is not good enough, I will do another try with a "+" button to display the hidden icons |
@seballot any chance you can get this work done within 24 hours? I am rolling out a site for corona and it's going to be publicly facing and I want to use the new UI :) |
Hi @JohnMcLear! |
I am going to accept the changes at #3709, since it fixes a problem, is good enough, is compatible with both skins and has a consistent behaviour when there are many toolbar buttons. However, I would prefer if in the next release we could land the "+" sign instead of the scrolling, as I think it is more explicit, and - thus - discoverable. A future PR would be welcome, thanks. :) n.b.: actually, I had to reject the PR and directly commit on top of |
We have a new proposal for the toolbar (#3726). If we accept it, #3709 (right toolbar going on the bottom on both skins) will be reverted. The legacy skin will retain its original behaviour (the incons will get smaller) and Colibris will gain a "+" icon when overflowing. I still did not try it. Discussion in the PR. |
I love the new default skin but it needs polish, especially around when the browser width is < 400px as you lose formatting buttons etc. Afaik this was all handled before so should be handled with any new versions with a copy/paste :)
The text was updated successfully, but these errors were encountered: