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
Altair menu dropdown displays over entire chart #2208
Comments
This is a known issue (see #1845, #1916, #1923, #1938, #2123, etc.) and is happening due to CSS defined elsewhere in your jupyterlab frontend, either in a labextension or the cell output of a notebook in the current session. To address this, follow the steps here: #2123 (comment) I have never been able to reproduce this issue, and so have not been able to identify the root cause or work on a fix. If you're able to use your browser tools to find the source of the offending CSS, please let me know! |
Thanks for the solution! And apologies that I missed the known issue. I wasn't able to find the exact CSS via browser tools, but one thing I have in common with others who have experienced this problem is the use of Jupyter Widgets. In particular, I was using the following in another instance of Jupyter Lab. options_layout = ipywidgets.Layout(
overflow='auto',
border='1px solid black',
width='300px',
height='300px',
flex_flow='column',
display='flex'
) The options menu using flexbox as well, so perhaps this is related? |
Nice - thanks for the clue! I'll see if I can reproduce it from that. |
I recently upgraded one of my Conda environments to 4.1.0, and after doing so I immediately started getting the following display issue.
The "three dot" menu displays over the entire chart, and so whenever I mouseover the chart the menu becomes opaque, obscuring the chart. This effect persists on any chart I create in this notebook, and is not affected by chart size. The issue also persists after restarting jupyter lab.
I am using:
jupyterlab 1.2.6
jupyter_client 6.1.3
altair 4.1.0
I have Altair 4.1.0 on several other environments on this machine, and none of them have had this problem.
Thanks in advance!
The text was updated successfully, but these errors were encountered: