[BUG] Graphs excluded from print pages if they have over 1000 datapoints
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Tranquilo
- Stack tecnológico
- plotly, python
- Área
- data-visualization, frontend
Línea de trabajo
Comienza con la aplicación de ejemplo proporcionada y varía num_points alrededor de 1000. Después, reproduce la impresión mediante la impresión del navegador y html2pdf en Chrome, Edge y Firefox. Inspecciona el renderizado de dcc.Graph y la configuración de assets/html2pdf; se considera completado cuando el gráfico sigue siendo visible y se escala correctamente en la salida impresa para más de 1000 puntos.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Context
When saving a Dash app as a pdf dcc.Graph behaves wonky if the graph contains more than 1000 datapoints (starting at 1001 points). The actual graph doesn't appear properly in the printed page. Instead, an empty graph is shown (or it could be that the background is printed over the graph).
I tested the behavior in Firefox, Chrome and Edge, and the behavior is different per browser. I tested both printing the page via the browser print page functionality and via the html2pdf library.
In Chrome and Edge, the browser print page functionality works fine with more than 1000 datapoints. In Firefox, the datapoints are gone, and the print preview shows an empty plot.
Using the html2pdf library, all browser have issues. In Chrome and Edge, the plot line seems to have a different scale and is hidden behind the plot background. In Firefox the plot line is completely gone, just showing an empty plot. It could be that it is hidden behind the plot background as well but that the scale is smaller so we don't see it.
It's possibly a bit of an edge case that might not be due to Dash. If it is not, please consider documenting this limitation somewhere.
Expected behavior
The plot should be visible on the printed page regardless how many points are in the plot.
Example app
To reproduce the behavior, take this example app for generating a simple plot and play around with num_points.
import dash
from dash import dcc, html, clientside_callback, Input
import plotly.express as px
import numpy as np
app = dash.Dash(__name__)
num_points = 2000
x = np.linspace(0, 10, num_points)
y = np.sin(x) * 100 + np.random.normal(0, 5, num_points)
fig = px.line(
x=x,
y=y,
title="Line Chart",
)
app.layout = html.Div(
id="main_container",
children=[
html.H1("Plotly Dash App"),
dcc.Graph(figure=fig),
html.Div(
children=[
dcc.Button(
id="save_as_pdf",
children="Save as PDF",
)
],
),
]
)
clientside_callback(
f"""
function (button_clicked) {{
if (button_clicked && button_clicked > 0) {{
var mainContainerElement = document.getElementById("main_container");
var opt = {{
// margin units are those that are defined in jsPDF key below.
margin: 10,
filename: 'test_file.pdf',
image: {{ type: 'jpeg', quality: 0.98 }},
html2canvas: {{
scale: 3,
width: 1920,
dpi: 300,
}},
jsPDF: {{ unit: 'mm', format: 'A4', orientation: 'p' }},
// pagebreak: {{ mode: ['avoid-all'] }}
}};
html2pdf().from(mainContainerElement).set(opt).save();
}}
}}
""",
Input(component_id="save_as_pdf", component_property="n_clicks"),
)
if __name__ == "__main__":
app.run(debug=True)
Setup
dash 4.0.0
dash-core-components 2.0.0
dash-html-components 2.0.0
dash-table 5.0.0
plotly 6.5.2
numpy 2.4.4
Take html2pdf from here: https://github.com/eKoopmans/html2pdf.js/blob/main/dist/html2pdf.bundle.min.js and put it in the assets folder next to the example app.
-
Browser, Version and OS
- OS: Windows
- Browser:
- Chrome: 150.0.7871.114
- Firefox: 152.0.4
- Edge: 150.0.4078.48
Screenshots
Edge/Chrome with 2000 points
Print page (this is also how it shows in all cases when number of points <= 1000)
html2pdf
Firefox with 2000 points
Print page
html2pdf
- Lenguaje dominante
- Python
- Estrellas
- 24.4k
- Forks
- 2.3k
- Merge medio
- 1 d 21 h
- PR fusionados (30 d)
- 19
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de plotly/dash
-
good first issue P3 size: 1 task
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
enhancement P2 size: 5
Dificultad 5/5 Más de una semana Aptitud para principiantes 45/100
-
enhancement P3 size: 10+
-
P2 size: 1 task
-
enhancement P3 size: 1
Dificultad 3/5 1-2 días Aptitud para principiantes 72/100
Todos los issues de plotly/dash
Issues similares
-
essnmx good first issue
Dificultad 1/5 Menos de una hora Aptitud para principiantes 95/100
-
[Feature] 奇物选择添加优先级 Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
syfoud/Simulated_Scepter#174 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Giskard-AI/giskard-oss#2840 · 1 comentario ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Abiertoarea: repo bug perceived difficulty: 2
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
yeti-platform/yeti#1380 ·