This repository has been archived by the owner on Sep 11, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 78
Chart Range: Gets destroyed on click when no timestamp is present #100
Comments
Any info on when this will be addressed? |
4 tasks
Currently working on this bug. All our logic (event listeners and handling) is based on that there can exist a timestamp and a range so it makes it hard to fix this bug. Will require some rewrites of the core functionality of the selection area. |
lukasholzer
pushed a commit
that referenced
this issue
Feb 3, 2020
Fixes #100. Fixes an issue where the chart selection of a time-frame was destroyed when a click somewhere else in the chart was performed.
lukasholzer
pushed a commit
that referenced
this issue
Feb 3, 2020
Fixes #100. Fixes an issue where the chart selection of a time-frame was destroyed when a click somewhere else in the chart was performed.
@lukasholzer, thanks for the heads-up! |
lukasholzer
pushed a commit
that referenced
this issue
Feb 4, 2020
Fixes #100. Fixes an issue where the chart selection of a time-frame was destroyed when a click somewhere else in the chart was performed.
github-actions bot
pushed a commit
that referenced
this issue
Feb 4, 2020
Fixes #100. Fixes an issue where the chart selection of a time-frame was destroyed when a click somewhere else in the chart was performed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If no timestamp is present we should not destroy the range. Filter out the click and ignore it if no timestamp is set
The text was updated successfully, but these errors were encountered: