Skip to content
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

Push status is truncated #6956

Closed
gingerbeardman opened this issue Feb 27, 2019 · 5 comments
Closed

Push status is truncated #6956

gingerbeardman opened this issue Feb 27, 2019 · 5 comments
Labels
design-input-needed Issues that require design input from the core team before the work can be started enhancement

Comments

@gingerbeardman
Copy link
Contributor

gingerbeardman commented Feb 27, 2019

Please describe the problem you think should be solved

Push status is truncated in the narrow "tab" element:
screen shot 2019-02-27 at 10 38 13

There is lots of room in the window, the size of this tab seems artificially limited.

Workaround: mouse over to see tooltip. Not a great solution.

[Optional] Do you have any potential solutions in mind?

The "tab" should take up the whole available width.

@shiftkey
Copy link
Member

@gingerbeardman thanks for the feedback! I'll also cross-reference #4569 which talks about making the branch switcher expand to fill the available space.

@shiftkey shiftkey added enhancement design-input-needed Issues that require design input from the core team before the work can be started labels Feb 27, 2019
@tierninho
Copy link
Contributor

Given that rebasing is on the roadmap, it seems reasonable to re-examine this again as this is not ideal.

The end user should be provided with complete context upon first glance.

screen shot 2019-02-28 at 10 02 50 am

@milholen
Copy link

I was going to submit the same issue, good to see that I'm not the only one who noticed this. IMO it would be best to handle the Branch and Fetch/Push/Pull as dynamic columns that are each 50% of the available width.

Mac Desktop screenshot:

space

@steveward
Copy link
Member

Closing in favor of #17388 and #18095 is also open to address this.

@gingerbeardman
Copy link
Contributor Author

@steveward I'm glad the problem has got some attention after 10,000 issues and 4+ years

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design-input-needed Issues that require design input from the core team before the work can be started enhancement
Projects
None yet
Development

No branches or pull requests

5 participants