[Vis] [Controls] [Firefox] After applying 2+ filters, their labels continuously changing order and impossible to clear values and re-apply changes

[dmlemeshko]

Kibana version: master

Elasticsearch version: master

Server OS version:

Browser version: Firefox 68.0

Browser OS version: MacOS 10.14.5 (Mojave)

Original install method (e.g. download page, yum, from source, etc.): master

Describe the bug:

Steps to reproduce:

1. Visualisations -> create new Controls E
2. Set 2 controls (e.g. logstash-* index pattern, geo.src & clientip fields)
3. Select values for fields and apply changes

Filters applied, but continuously changing order. It is impossible to clear input fields

Note: cannot reproduce on Chrome 75

Expected behavior: Filters are applied and static. It is possible to clear inputs and apply new filters.

Screenshots (if relevant):

Errors in browser console (if relevant): no any js errors in the console

Provide logs and/or server output (if relevant): no errors on Kibana server-side

Any additional context:

[elasticmachine]

Pinging @elastic/kibana-app

[dmlemeshko]

Reproduced on 7.x/7.4

[marius-dr]

Also in 7.3.0

[ansell]

This is also occurring consistently for me, as a new regression with Kibana-7.3.0, on Firefox (tested 68.0.1 on both MacOS and Ubuntu) with Filter's on all Dashboards and Discover searches in addition to Visualizations.

One anomaly that I noticed compared to Safari (where the bug doesn't appear) is a large number of calls to /elasticsearch/_msearch?rest_total_hits_as_int=true&ignore_throttled=true. These calls seem to be duplicated each time they occur and they continue to occur every 10-20 seconds without stopping, where in Safari there are two calls initially and then no further activity on the same dashboard/search/visualisation.

[kertal]

I've researched this bug yesterday, reproduced it in 7.3.0, found the code that caused it, it's fixed in 7.3.1 + 7.x. @dmlemeshko could you please confirm it, so we can close this issue

[kertal]

should be fixed by #41999

[dmlemeshko]

@kertal I may confirm it has been fixed (master, 7.x & 7.3.1), I merged a PR with functional tests that may help to catch it next time.

[kertal]

@dmlemeshko perfect! thx