You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is not a major issue, but I think it is nice to improve.
Original jvector library provides a hover which can follows the position of mouse like this:
However, the hover in kibana map panel doesn't. It always display at the left top corner, no matter where your mouse is pointing
The reason of it is that kibana is using its own fix-positioned 'map-legend' instead of the original 'jvectormap-label'. However, both of them are defined in https://github.com/elasticsearch/kibana/blob/master/src/app/panels/map/module.html
though jvectormap-label is not being used. ( I understand the reason to use map-legend rather than 'jvectormap-label' is because 'jvectormap-label' doesn't support multipanel.)
Maybe we can improve it or at least clean up the unused code?
The text was updated successfully, but these errors were encountered:
Hey @xingwx, while Kibana 4 doesn't include a map yet, we will make sure this issue doesn't exist in the map that is coming. If you experience any further issues please feel free to file an issue. Thanks!
It is not a major issue, but I think it is nice to improve.
Original jvector library provides a hover which can follows the position of mouse like this:
However, the hover in kibana map panel doesn't. It always display at the left top corner, no matter where your mouse is pointing
The reason of it is that kibana is using its own fix-positioned 'map-legend' instead of the original 'jvectormap-label'. However, both of them are defined in https://github.com/elasticsearch/kibana/blob/master/src/app/panels/map/module.html
though jvectormap-label is not being used. ( I understand the reason to use map-legend rather than 'jvectormap-label' is because 'jvectormap-label' doesn't support multipanel.)
Maybe we can improve it or at least clean up the unused code?
The text was updated successfully, but these errors were encountered: