Errorbars on scatter plots don't react to point selection
維護者通常 1 天內回覆
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 48/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- javascript
研究方向
從連結的 CodePen 重現開始,檢查散佈圖誤差條在選取資料點時相對於標記和線條是如何繪製的。將其行為與柱狀圖中的誤差條進行比較,然後確認選取資料點也會改變相關的誤差條,而不會獨立選取誤差條。
由索引模型根據 Issue 內容生成。
描述
If you make a plot with errorbars, they aren't affected at all by selections. This both looks weird (like part of your point was left behind when it became deselected) and can cause usability problems, in that it's harder to distinguish selected and unselected points, particularly if the points themselves are small.
The simple solution here would be to include the errorbars in the group that responds to marker.opacity. That also seems the most correct, as you shouldn't see an errorbar through a partially transparent marker, and intuitively I'd expect errorbars to become transparent along with their associated markers. I think that would cover most use cases, though including some errorbar attributes like color and thickness in the selected and unselected styles would also be nice.
A tricky bit here is that normally errorbars are drawn behind lines but markers are in front of lines, so they can't just be combined with the markers. I suspect the right solution is to only put them behind the lines when there are no markers, but when there are markers bring them up to just behind and grouped with each marker.
Relatedly, no errorbar attributes other than array and arrayminus accept arrays. Enabling color in particular to be an array would be useful, and could mostly work around the main issue here in some cases, though I wouldn't call it a full solution.
https://codepen.io/alexcjohnson/pen/RNbGamp?editors=0010
To be clear: I don't think we should select the errorbars themselves - just select the points and bring the errorbars along for the ride.
Interestingly, errorbars on bar charts already behave correctly:
- 主要語言
- JavaScript
- 星號
- 18.4k
- 分支
- 2k
- 平均合併
- 3 天 23 小時
- 30 天內合併 PR
- 15
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
plotly/plotly.js 的其他 Issue
-
bug P3 size: 3
難度 2/5 1-3 小時 新手友好度 86/100
plotly/plotly.js#8108 · 1 則留言 ·
維護者通常 1 天內回覆
-
chore P3 plotly-internal size: 3 task
難度 2/5 1-3 小時 新手友好度 77/100
plotly/plotly.js#8064 · 1 則留言 ·
維護者通常 1 天內回覆
-
chore P1 plotly-internal size: 1 task
難度 1/5 1 小時以內 新手友好度 82/100
維護者通常 1 天內回覆
-
chore P3 plotly-internal size: 1 task
難度 2/5 1-3 小時 新手友好度 65/100
維護者通常 1 天內回覆
-
[mkdocs] Update link in Edit this Page button可能重新可做 @AbhinavKumar-Jha 於 143 天前認領,目前沒有進行中的 PR。 未關閉bug
難度 2/5 1-3 小時 新手友好度 65/100
plotly/plotly.js#7648 · 3 則留言 ·
維護者通常 1 天內回覆
相似的 Issue
-
factory-active factory-automatic task-bug-reproduction-success task-identify-harness-labels-done task-identify-issue-type-done
難度 2/5 1-3 小時 新手友好度 62/100
維護者通常 1 天內回覆
-
documentation
難度 2/5 半天 新手友好度 78/100
facioquo/stock-indicators-dotnet#2300 ·
維護者通常 1 天內回覆
-
good first issue needs-triage priority: low
難度 2/5 1-3 小時 新手友好度 82/100
melodic-software/claude-code-plugins#6982 · 1 則留言 ·
維護者通常 1 天內回覆
-
val() setter uses the first control's type for a mixed selection可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉
難度 2/5 半天 新手友好度 85/100
維護者通常 1 天內回覆
-
難度 1/5 1-3 小時 新手友好度 75/100
douglascrockford/Misty#35 ·
維護者通常 1 天內回覆