Open lucianbaciu opened 1 month ago
this change was intentional to avoid triggering mouse events that uplot listens to while the user interacts with third-party dom elements that are added into .u-over
(like an anchored tooltip). it was introduced in https://github.com/leeoniya/uPlot/commit/bab8c11a10f5c3e884f8f1d863826dd2996d1ed2
you should be able to restore the previous behavior by overriding cursor.bind.*
with functions that dont do any event target filtering:
a different, probably better approach is to set css pointer-events: none
on the highlight region but keep the grip portion responding to events like normal.
pointer-events: none
could be an option, but I'm not sure if it's possible
u-select::before is the blue part. u-select is capturing the event. If I set it as pointer-events: none
, the grips (which are children) will be also disabled. If I disable events only in the ::before, the main u-select
is eating the event
am I missing something?
ah yeah, i forgot the demo implements the grips as select children. then you're right, you can't use the css strategy.
i'm leaning towards adding the .u-select
into the current filter, since it is also "native" to uPlot, like .u-over
. hopefully it doesnt affect perf too much to check against two elements during mousemoves vs just one. in most cases i think we can bypass the check when the select size is 0.
thank you! I will try
In 1.6.21 this does not exist.
In the latest versions, while hovering a time selection, the position line event is not working.
The line is moving well when hovering outside of the blue selection