FigureWidget missing update for annotations/static lines
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18.8k
- Forks
- 2.8k
- Avg merge
- 16h 26m
- Merged PRs (30d)
- 21
Description
I use a FigureWidget as container for an updating Figure within JupyterLab. When I update the FigureWidget within a batch_update, the data and the layout overall are updated, but if I introduced a static object like a vline, this persists on the graphic. New executions of the very same FigureWidget instance show the refreshed frame. The properties of the instance itself are also indeed correctly update. Only the old frame in the previous executed cell misses the update on the static lines (but the data and other parts of the layout are correctly update every time as expected).
Here the basic code for reproducing the bug:
import plotly.graph_objects as go
import ipywidgets as wdgt
from plotly import __version__
print(f"Plotly: {__version__}")
print(f"IPywidgets: {wdgt.__version__}")
fig_wdgt = go.FigureWidget()
fig_wdgt
fig = go.Figure()
# fig.add_trace(go.Scatter(x=[1, 2, 3], y=[2, 1, 3]))
# fig.add_vline(x=2, annotation_text="my test line")
with fig_wdgt.batch_update():
fig_wdgt.data = []
fig_wdgt.layout = {}
fig_wdgt.add_traces(fig.data)
fig_wdgt.layout = fig.layout
and here screenshots with the bug, and suggested use of the code within Jupyter cells:
I tested the behaviour with python 3.10, Plotly: 5.15.0 and IPywidgets: 8.0.4, on OS, Linux, Windows, and on both Chrome and Edge browsers.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the FigureWidget and batch_update reproduction in the issue, using the stated Python, Plotly, and ipywidgets versions in JupyterLab. Compare updates to data, layout, and static objects such as vlines; done means the previously executed cell refreshes its annotations and static lines without requiring a new execution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, python
- Domain
- data-visualization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100