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

Consistent width for fullscreen button and time-control #2893

Closed
wants to merge 2 commits into from

Conversation

hartman
Copy link
Contributor

@hartman hartman commented Dec 7, 2015

This changes the width of the fullscreen button to 4em. For some
reason it was 3.8, but that doesn't make much sense and is not in line
with the other controls.

It also sets the textual time-control's width to auto with a 1em
padding to the left and right. Again this is more in line with the
behavior of the other controls.

I do find the entire interface slightly too wide to my liking, but that is exactly why it should be consistent, so that if required, it would be easier for me to override.

This changes the width of the fullscreen button to 4em. For some
reason it was 3.8, but that doesn't make much sense and is not in line
with the other controls.

It also sets the textual time-control's width to auto with a 1em
padding to the left and right. Again this is more in line with the
behavior of the other controls.
@gkatsev
Copy link
Member

gkatsev commented Feb 2, 2016

LGTM. Thanks.

@gkatsev gkatsev added patch This PR can be added to a patch release. needs: LGTM Needs one or more additional approvals labels Feb 2, 2016
@dmlap
Copy link
Member

dmlap commented Feb 4, 2016

LGTM

@gkatsev gkatsev added confirmed and removed needs: LGTM Needs one or more additional approvals labels Feb 4, 2016
@gkatsev gkatsev closed this in 171ec1a Feb 4, 2016
@hartman hartman deleted the controls_width branch May 10, 2016 11:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
confirmed patch This PR can be added to a patch release.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants