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

Notebook cell weirdness in 3.0rc11 #9423

Closed
jasongrout opened this issue Dec 3, 2020 · 3 comments · Fixed by #9427
Closed

Notebook cell weirdness in 3.0rc11 #9423

jasongrout opened this issue Dec 3, 2020 · 3 comments · Fixed by #9427
Labels
status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Milestone

Comments

@jasongrout
Copy link
Contributor

Description

We're seeing very weird behavior for notebook cells in 3.0rc11. Note that the cell automatically getting longer right when it is created is something automatic, I'm not doing anything at first. Then typing new characters doesn't seem to work properly either.

cell

Current hypotheses are that this is a problem with #9407, since the recent codemirror changes all seem to have been made in the 2.3.x branch.

Reproduce

  1. Install 3.0rc11
  2. create new notebook, try to add a cell and type text into the cell

Expected behavior

Things to work like in 3.0rc10 - cells appropriate size, typing a cell to show the text typed, etc.

Context

  • Operating System and version: macos Catalina
  • Browser and version: Firefox 83
  • JupyterLab version: 3.0rc11
Troubleshoot Output
Paste the output from running `jupyter troubleshoot` from the command line here.
You may want to sanitize the paths in the output.
Command Line Output
Paste the output from your command line running `jupyter lab` here, use `--debug` if possible.
Browser Output
Paste the output from your browser Javascript console here.
@jasongrout jasongrout added this to the 3.0 milestone Dec 3, 2020
@jasongrout
Copy link
Contributor Author

I'm not seeing any 404s with files, so it doesn't seem that we just aren't including files in the package.

@jasongrout
Copy link
Contributor Author

jasongrout commented Dec 3, 2020

I'm seeing the same thing in current master: b2af792, and don't see it on a previous commit. I'm bisecting now...

@jasongrout
Copy link
Contributor Author

jasongrout commented Dec 3, 2020

Investigating, I see that our logic of substituting a js file in for a css file is causing problems. For example, in

import 'codemirror/lib/codemirror';
we see that we are preferring to import the codemirror js instead of the codemirror css, but we really do want the css.

One way to deal with this is to make our substitution logic smarter. Only import the js file if it only has import statements, for example.

Or even better, let's just make it an explicit opt-in - a separate jupyterlab js style key that we prefer over the package.json style key.

@github-actions github-actions bot added the status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. label Jun 3, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant