Open rriemvis opened 2 years ago
Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors)
@flash1293 : in my opinion this is still a bug: why should a map reload occur when you update the Kibana time filter from within the Vega script (while not changing any map settings/signals)? This behavior is not logical and prevents dynamic updates in combination with a map. Correct functioning of this allows for live updates of data on a map dashboard for example.
@rriemvis I understand how the behavior you describe would be an improvement, however I checked an old version of Kibana and it seems like vega maps never behaved any differently than they do right now - it's on the edge between enhancement and bug for me.
Anyway, the categorization doesn't matter too much. I will raise this with the team and get back to you shortly. Unfortunately the enhancement isn't super simple to implement based on how the code is structured, but I agree that it would be a much better user experience to just update the data and not the whole map instance.
Kibana version: 8.4.0/8.4.1
Elasticsearch version: 8.4.0/8.4.1
Server OS version:
Browser version: Chrome 105.0.5195.102 64 bits
Browser OS version: Window 10 Pro 21H2
Original install method (e.g. download page, yum, from source, etc.):
Describe the bug:
When you include a map on a Vega custom script and you modify the Kibana Time filter with the function kibanaSetTimeFilter(...), the map tiles are reloaded at every call of this function. This is very annoying as it looks like a page reload and the map-scale, map-center is not modified at all.
Steps to reproduce:
The following minimal script generates the described behavior:
Expected behavior:
No effect on the map loading when the kibana time filter is called.
Screenshots (if relevant):
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Any additional context: