tabs not rendering properly in Jupyterlab 4.0.1 #3785
Comments
|
Can confirm problem continues on Jupyterlab 4.0.2. |
|
I have narrowed the tabs not rendering down to styles defined by PhosphorJS, or rather the symptom goes away when you add these styles back to the widget. See the video below. I have tried to add these deprecated style class names to phosphor-styles.webm |
|
After running @martinRenou's PR #3787 the problem is resolved. In |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
This has been tested in the 'fresh environment' suggested and still occurs. However, most of the information in this report is for my particular environment.
Using the following code in jupyter lab (either in browser OR VScode):
results in the requested tabs NOT rendering properly. Instead showing no 'boundary' around the tab titles. In fact, the titles just appear as text on a line above the tab contents. The tabs themselves still work in that clicking on them does switch the contents being viewed, so this is a cosmetic defect as shown below:
Reproduce
Expected behavior
We expect the tabs to be rendered with boundary lines between them as occurs when the same code is run in jupyterlab version 3.5.6, as shown below:
Context
My full jupyter environment (as output by
!jupyter --version) where this tab rendering failure occurs is provided here:I have confirmed this script renders the tabs correctly in jupyterlab 3.5.6 with the following jupyter environment
The only differences between the two environments are the
jupyterlabandjupyter_serverversions.Troubleshoot Output
Paste the output from running `jupyter troubleshoot` from the command line here. You may want to sanitize the paths in the output.Browser Output
Clearing the Javascript Console and then performing a 'Restart kernel and run all cells` produced the following output in the Javascript Console:Kernel: restarting (8fa40505-2b6a-418c-88a8-b637105545fd) jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 Connection lost, reconnecting in 0 seconds. _reconnect @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 reconnect @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 restart @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 await in restart (async) restartKernel @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 restart @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 await in restart (async) execute @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 execute @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 execute @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 execute @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 triggerActiveItem @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 _evtMouseUp @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 handleEvent @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 Starting WebSocket: ws://localhost:8889/api/kernels/8fa40505-2b6a-418c-88a8-b637105545fd jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 TypeError: Cannot read properties of undefined (reading 'widget') at isReady (jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1:1054549) at jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1:872986 at b (jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1:873080) at P.onKernelChanged (jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1:1053706) at m (jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1:1646566) at Object.l [as emit] (jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1:1646242) at a.emit (jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1:1644079) at b.restartKernel (jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1:127003) at async y.restart (jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1:134701) at async execute (jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1:65675) onKernelChanged @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 await in onKernelChanged (async) m @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 l @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 emit @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 restartKernel @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 await in restartKernel (async) restart @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 await in restart (async) execute @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 execute @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 execute @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 execute @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 triggerActiveItem @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 _evtMouseUp @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 handleEvent @ jlab_core.b473ae48d19e9025bb00.js?v=b473ae48d19e9025bb00:1 150.1a6d6a3a0542a41bec5a.js?v=1a6d6a3a0542a41bec5a:1 Failed to fetch ipywidgets through the "jupyter.widget.control" comm channel, fallback to fetching individual model state. Reason: Control comm was closed too earlyIf using JupyterLab
Installed Labextensions
Paste the output from your command line running `jupyter labextension list`.JupyterLab v4.0.1 /Users/juan/miniconda3/envs/stellardev_alt/share/jupyter/labextensions jupyterlab_pygments v0.2.2 enabled X (python, jupyterlab_pygments) ipyevents v2.0.1 enabled OK @jupyter-widgets/jupyterlab-manager v5.0.7 enabled X (python, jupyterlab_widgets)The following extensions are outdated:
jupyterlab_pygments
@jupyter-widgets/jupyterlab-manager
Consider running "jupyter labextension update --all" to check for updates.
The text was updated successfully, but these errors were encountered: