Skip to content

Add button to expand tabs in the sidebar#558

Closed
danxuliu wants to merge 2 commits into
masterfrom
add-button-to-expand-tabs-in-the-sidebar
Closed

Add button to expand tabs in the sidebar#558
danxuliu wants to merge 2 commits into
masterfrom
add-button-to-expand-tabs-in-the-sidebar

Conversation

@danxuliu

Copy link
Copy Markdown
Member

Due to the scroll bar being shown only for the tabs the call details are always visible. In short screens this may not leave too much space for the tabs, making them uncomfortable to use.

To improve that now a button is added automatically to every tab added to the sidebar; clicking on the button toggles the associated tab between its normal size and an expanded size that fills the whole sidebar.

I have tried other approaches, like hiding the call details when scrolling in one direction and showing it back when scrolling on the opposite direction, but in the end the button one was the simplest, most reliable and less bug/quirk prone.

The ElementExpanderButton is a helper class to expand (and restore) an
element in an ancestor.

It works directly on HTML elements and it does not take into account
Backbone or Marionette views; it simply traverses the ancestors of the
expandable element hiding their siblings until the container is reached.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Due to the scroll bar being shown only for the tabs the call details are
always visible. In short screens this may not leave too much space for
the tabs, making them uncomfortable to use. To improve that now an
ElementExpanderButton is added automatically to every tab added to the
sidebar; clicking on the button toggles the associated tab between its
normal size and an expanded size that fills the whole sidebar.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
@jancborchardt

jancborchardt commented Jan 10, 2018

Copy link
Copy Markdown
Member

Hum, this is adding a confusing mode which needs another action/icon on top.

Rather than that, it seems like here we should:

@jancborchardt

jancborchardt commented Jan 10, 2018

Copy link
Copy Markdown
Member

Aaaand see:

@jancborchardt jancborchardt left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See comment #558 (comment)

This is too much UX-wise, and we should rather clean up the header as per #562

@nickvergessen nickvergessen modified the milestones: 3.0 (Nextcloud 13.0.0), 3.1 (Nextcloud 13.0.2/3) Jan 10, 2018
@nickvergessen

Copy link
Copy Markdown
Member

bildschirmfoto von 2018-01-10 13-02-41

@danxuliu

Copy link
Copy Markdown
Member Author

@nickvergessen I know that it is going to sound surprising... but that is by design. If the icon is in a lower position it would seem to be part of the Add participant field. If it is in a higher position it could overlap with the tab header. The idea was to float it there so it is seen as a separate element... but if you think that it is a bug it seems that the idea failed miserably :-P

@danxuliu

Copy link
Copy Markdown
Member Author

Closing. See #493 (comment)

@danxuliu danxuliu closed this Jan 12, 2018
@nickvergessen nickvergessen deleted the add-button-to-expand-tabs-in-the-sidebar branch February 14, 2018 15:16
marcoambrosini pushed a commit that referenced this pull request Oct 9, 2019
Remove unused isFocusable computed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature: chat 💬 Chat and system messages

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants