Adding second filter in discover causes erratic behaviour.

[jfwvv]

Kibana version:
7.3.0
Elasticsearch version:
7.3.0
Server OS version:
Ubuntu 18.04 LTS
Browser version:
Firefox 68.0.1
Browser OS version:
Ubuntu 18.04 LTS
Original install method (e.g. download page, yum, from source, etc.):
apt (with deb https://artifacts.elastic.co/packages/7.x/apt stable main)
Describe the bug:
Adding a second filter to the list of filters causes both to quickly and continously swap position.
Also the time indicator starts running quickly. Visualize misbehaves in a similar manner.
Steps to reproduce:

1. Click on the discover icon to go to Discover; wait for it to load. Stop any refresh to not confuse things.
2. Add a filter by any means desired. Manually Add filter or click on any Filter (for|out) value magnifying glass.
3. Wait for filter to be applied
4. Add a second filter by any means.
5. Observe errattic flipping behaviour. Filter dos not seem to be applied.

Expected behavior:
When adding a second filter it should stay in position, the filter should be applied. The result shoud be shown and the period should not start advancing by itself.

Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:

• Managing to close either filter by clicking at the correct time at one of the closing buttons of any of these two filters restores sane behaviour with one filter active.
• Adding a 3rd filter does not improve or worsen the symptoms.

[cRUSHr2012]

Same here, on CentOS 7.6, Kibana + Elasticsearch 7.3.0, upgraded from 7.2
Installed originally with yum, then updated via yum update.
Using Firefox 68.0.1 on MacOS 10.14.6
Safari does not have this problem.

[jfwvv]

Chromium (version 76.0.3809.87) on my Ubuntu 18.04 LTS also behaves correctly.

[Moonbeam4520]

same here, kibana 7.3.0, firefox 68.0.1 on Ubuntu 18.04.3
on Chromium it behaves correctly

[v01t]

Same behavior using firefox 68.0.1, using Chrome 76.0.3809.87 filters behaves correctly

[vedard]

I got the same behavior with Firefox, a workaround is to click the back button when this happens

[kertal]

Thanks a lot for reporting this. it has been already fixed by #41999.
Fix will be part of Kibana 7.3.1, it is Firefox specific, so a temporary workaround is using another browser