pissang edited a comment on issue #15775:
URL: https://github.com/apache/echarts/issues/15775#issuecomment-996653758
Sorry for accidentally closing this issue. Didn't remember how I did this.
I just want to make sure the use case make sense before we exposing a new
event or other APIs. It's easy to have forward compatiblity issues. What if we
have more use cases in the future but have conflicts with the current exposed
API?
For example, when I click the `dataZoom`, what I expected is getting the
`percent` of the point I clicked so I could do more things like move to this
range, just like other events. But I don't think clicking on the dataZoom area
to fetch more data is an intuitive user interaction.
Especially when it having conflicts with our builtin user interaction that
`click to select'. The selected window will be changed after I clicked the
dataZoom. So what range should it use to fetch the data, the new one or the old
one?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
