plotly / plotly/plotly.js

[BUG]: selectedpoints for curvenumber > 0 invisible when using scattergl

Open
#7,728 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
18.3k
Forks
2k
Avg merge
2d 12h
Merged PRs (30d)
28

Description

Description

When setting selectedpoints on a scattergl trace for curvenumbers > 0, the markers disappear - for curvenumber 0 it works as expected.

Screenshots/Video

Works as expected:
var curveNumber = 0;
var selected = [0, 1, 2];
Image

Selected markers disappear:
var curveNumber = 1;
var selected = [0, 1, 2];
Image

Steps to reproduce

Please switch between curveNumber = 0 and curveNumber = 1

https://codepen.io/ismirsehregal/pen/gbwgOWm

Notes

Error messages in the browser console:

(index):1 [.WebGL-0x25640015b100] GL_INVALID_OPERATION: Error: 0x00000502, in ....\third_party\angle\src\libANGLE\renderer\renderer_utils.cpp, rx::ComputeStartVertex:1591. Internal error: 0x00000502: Integer overflow.
(index):1 [.WebGL-0x25640015b100] GL_INVALID_OPERATION: Error: 0x00000502, in ....\third_party\angle\src\libANGLE\renderer\d3d\VertexDataManager.cpp, rx::VertexDataManager::reserveSpaceForAttrib:535. Internal error: 0x00000502: Vertex buffer is not big enough for the draw call.

I posted the issue here first. However, this seems to be a plotly.js bug.
This might be related.

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.

Research direction

Start with the linked CodePen reproduction and compare scattergl behavior for curveNumber 0 and 1 when selectedpoints is set. Investigate the WebGL draw errors reported in the browser console and the possibly related issue #7271. Done means selected markers remain visible for nonzero curve numbers without the reported buffer errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
data-visualization
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.