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

CSS rules change default Phosphor overflow #3986

Closed
sccolbert opened this issue Feb 23, 2018 · 5 comments · Fixed by #6492
Closed

CSS rules change default Phosphor overflow #3986

sccolbert opened this issue Feb 23, 2018 · 5 comments · Fixed by #6492
Labels
bug good first issue pkg:tabmanager status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. tag:Design and UX
Milestone

Comments

@sccolbert
Copy link
Contributor

This rule changes Phosphor's default overflow visibility for the tab bars:

capture

Which results in this undesired overflow artifact:

capture

Restoring the default overflow rule fixes the problem:

capture

I have no insight as to why the default was changed.

CC @jasongrout @ellisonbg

@ellisonbg
Copy link
Contributor

ellisonbg commented Feb 23, 2018 via email

@sccolbert
Copy link
Contributor Author

sccolbert commented Feb 23, 2018

Looking at it more, it seems like the default was changed in order to "blend" the active tab with the tool bar. This is not the intended way to achieve that effect. The intended way is to make the active tab 1px taller, and translate it down 1px so that it overlaps the lower border. That's how it's done here: http://phosphorjs.github.io/examples/datagrid/

capture

@ellisonbg
Copy link
Contributor

Hmm, I thought we were doing it that way...

@saulshanabrook
Copy link
Member

I just confirmed this style causes a bug. I could reproduce it by creating a bunch of tabs and then dragging over the middle bar so they show up overflowing:

screen shot 2018-04-30 at 1 38 15 pm

If we remove this rule, they do not overflow:
screen shot 2018-04-30 at 1 38 36 pm

@saulshanabrook saulshanabrook added this to the Future milestone Sep 10, 2018
@jasongrout jasongrout modified the milestones: Future, 1.0 Sep 12, 2018
@saulshanabrook saulshanabrook removed their assignment Mar 20, 2019
jasongrout added a commit to jasongrout/jupyterlab that referenced this issue Jun 12, 2019
…e active tab

Fixes jupyterlab#6532
Reverts jupyterlab#6526
Reverts jupyterlab#6492


jupyterlab#3986 is now an issue again, but setting the tab min width to 0px (instead of 36px) and setting the tab overflow to hidden makes it less likely to appear in practice (i.e., the tabs need to be much denser now to overflow into the splitter). Setting the tab overflow to hidden also makes the close icon for tabs not overlap the next tab, which was very confusing.

I think this is the best compromise at this point.

I also experimented unsuccessfully with setting the z-index of the splitter handle in an attempt to get it to be on top of overflowing tabs.
@lock
Copy link

lock bot commented Aug 6, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related discussion.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 6, 2019
@jasongrout jasongrout added the status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. label Aug 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug good first issue pkg:tabmanager status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. tag:Design and UX
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants