plotly / plotly/plotly.R

event_data("plotly_hover") not triggering for full range of 3D surface

Open
#1,345 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

shiny
Dominant language
R
Stars
2.7k
Forks
641
PR merge metrics
No merged PRs in 30d

Description

I have a 3D space comprising four surfaces added as traces using add_surface. I hope to link these to a subplot using event_data("plotly_hover") (or event_data("plotly_click") ).

These events trigger correctly over some of the range of the surface, between x = 15 and 38 inclusive, but not the full range.

A more detailed description of the problem, including screengrabs showing event_data() working correctly and incorrectly, is provided here, along with a reproducible code example.

The desired use case for this feature is shown in the last two tabs of the app deployed here. The aim is in effect to perform 'tomography' on the surfaces along the age (x), year (y) and birth cohort axes (y-x). Within the range over which event_data triggers correctly this works really well.

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 reproducible code example in the linked Stack Overflow question and compare event_data("plotly_hover") and event_data("plotly_click") across the full add_surface range. Done means the events trigger consistently across all four 3D surfaces and the full x range, including values outside x = 15–38.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
data-visualization
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.