[BUG]: Some plots render incorrectly when using virtual-webgl in Chromium browsers
Nessuno ha ancora preso questa issue.
- Lingua principale
- JavaScript
- Stelle
- 18.3k
- Fork
- 2k
- Merge medio
- 2g 12h
- PR unite (30g)
- 28
Descrizione
Description
Some plots are rendering incorrectly (missing or muted colors) when using virtual-webgl in Chromium based browsers. This was originally reported in plotly/Kaleido#375.
Screenshots/Video
| Without virtual-webgl | With virtual-webgl |
|---|---|
See plotly/Kaleido#375 for more examples.
Steps to reproduce
- Start plotly.js devtools
- Open the mock 'gl2d_parcoords_constraints'
- Note that there are number of dark red lines on the left side of the plot
- Edit devtools/test_dashboard/index.html to include the following
<script>tag in the body<script src="../../node_modules/virtual-webgl/src/virtual-webgl.js"></script> - Reload the mock
- Note that a few of the dark red lines are now missing
Notes
- This bug was discovered when development of Kaleido v1 started
- The previous version of Kaleido (v0.2.1) used Chromium v88. Kaleido v1 uses the installed Chromium version (usually a pretty recent one).
- At some point between the release of Chromium v88 and Chrome v112 (the oldest Chrome for Testing available here), the bug was introduced
- It's unclear if it's a bug in Chromium, a bug in virtual-webgl, or a bug in plotly.js
- Firefox doesn't have the issue, though colors do appear to render a differently for some plots when using/not using virtual-webgl
- Chromium v147 shows the following console warnings when using virtual-webgl:
virtual-webgl.js:389 WebGLRenderingContext.canvas is not supported (anonymous) @ virtual-webgl.js:389 (anonymous) @ virtual-webgl.js:1008 virtual-webgl.js:389 WebGLRenderingContext.drawingBufferColorSpace is not supported (anonymous) @ virtual-webgl.js:389 (anonymous) @ virtual-webgl.js:1008 virtual-webgl.js:389 WebGLRenderingContext.unpackColorSpace is not supported (anonymous) @ virtual-webgl.js:389 (anonymous) @ virtual-webgl.js:1008 virtual-webgl.js:389 WebGLRenderingContext.drawingBufferFormat is not supported (anonymous) @ virtual-webgl.js:389 (anonymous) @ virtual-webgl.js:1008 - Firefox v145 shows the following console warnings when using virtual-webgl:
WebGLRenderingContext.canvas is not supported <anonymous code>:formatted:8942:27 WebGLRenderingContext.drawingBufferColorSpace is not supported <anonymous code>:formatted:8942:27 WebGLRenderingContext.unpackColorSpace is not supported <anonymous code>:formatted:8942:27 - virtual-webgl support was added in plotly.js in #6784
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Riproduci il problema con il mock gl2d_parcoords_constraints e lo script virtual-webgl aggiunto a devtools/test_dashboard/index.html. Confronta il comportamento interessato di Chromium con Firefox e con le versioni di Chromium indicate nel report, quindi determina se le linee mancanti hanno origine in Chromium, virtual-webgl o plotly.js; il lavoro è completato quando il grafico viene renderizzato in modo coerente con virtual-webgl.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- javascript
- Ambito
- data-visualization
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Tranquilla
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 42/100