VSCode renderer background not changing with style

Open
#503 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
jupyter-notebook, vscode

Research direction

Start by reproducing the issue in the VS Code renderer with a dark plot style, then read the related matplotlib/ipympl issue for context. The work is done when the renderer background matches the normal VS Code background or the selected plot style consistently.

Written by the indexing model from the issue text.

Description

Describe the issue

switched to dark plot style, background isn't changing. Ideally it would just match the normal vscode background, but copying the plot style would work too

image

image

Versions

3.9.12 (main, Apr  4 2022, 05:22:27) [MSC v.1916 64 bit (AMD64)]
ipympl version: 0.9.2

Selected Jupyter core packages...
IPython          : 7.30.1
ipykernel        : 6.6.1
ipywidgets       : 7.7.0
jupyter_client   : 7.1.0
jupyter_core     : 4.9.1
jupyter_server   : not installed
jupyterlab       : not installed
nbclient         : 0.6.4
nbconvert        : 6.5.0
nbformat         : 5.4.0
notebook         : 6.4.12
qtconsole        : not installed
traitlets        : 5.5.0

Known nbextensions:
  config dir: C:\Users\TeamD\.jupyter\nbconfig
    notebook section
      jupyter-js-widgets/extension enabled 
  config dir: C:\Users\TeamD\.conda\envs\subgame\etc\jupyter\nbconfig
    notebook section
      jupyter-matplotlib/extension enabled 
      jupyter-js-widgets/extension enabled 
      - Validating: ok
      - Validating: ok
      - Validating: ok

Jupyter command `jupyter-labextension` not found.

Maybe related?

https://github.com/matplotlib/ipympl/issues/25

Dominant language
Jupyter Notebook
Stars
1.7k
Forks
234
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from matplotlib/ipympl

All issues in matplotlib/ipympl

Similar issues

More Data Visualization issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.