Selecting a period in the discover histogram does not result in a refresh.

[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:
Clicking on a bar or selecting a time period in the in the discover histogram does not result in a refresh to the period.
Steps to reproduce:

1. Click on the discover icon to go to Discover; wait for it to load. (Use a kibana index with a time field to ensure you get the histogram)
2. Click on a bar in the Discover Histogram. (Period above it changes accordingly but no refresh to the period occurs)

Expected behavior:
I expected the display to automatically zoom in on the selected period (as did 7.2.x)
I could not find any evidence that this was a deliberate change so I assume this is a regression.
Screenshots (if relevant):

Errors in browser console (if relevant):
no errors
Provide logs and/or server output (if relevant):

Any additional context:
Clicking on the refresh button or waiting for an automaitc refresh period to end ultimately leads to the the display of the selected period but the extra click or wait is rather annoying.

[elasticmachine]

Pinging @elastic/kibana-app

[timroes]

cc @kertal This looks a lot like the issue I hit recently in our Zoom where the timerange was not updating properly anymore. Do you think you could have a look?

[kertal]

I will! Tim Roes <notifications@github.com> schrieb am Mo. 5. Aug. 2019 um 15:48:

…

cc @kertal <https://github.com/kertal> This looks a lot like the issue I hit recently in our Zoom where the timerange was not updating properly anymore. Do you think you could have a look? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#42583?email_source=notifications&email_token=AADRH2YHAX44LFPATRJCZ6DQDAVSZA5CNFSM4IJJGJC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3R3ZJY#issuecomment-518241447>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADRH26C6Y6VPLNU7Q72ZQLQDAVSZANCNFSM4IJJGJCQ> .

[kertal]

I could reproduce it, however it will be fixed when #36517 is merged

[timroes]

@kertal if this is on 7.3.0 we should find another fix nevertheless, that can be backported to 7.3.1, because this PR I think is too large too backport it to a patch version.

[kertal]

Oki!doki! Tim Roes <notifications@github.com> schrieb am Di. 6. Aug. 2019 um 09:35:

…

@kertal <https://github.com/kertal> if this is on 7.3.0 we should find another fix nevertheless, that can be backported to 7.3.1, because this PR I think is too large too backport it to a patch version. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#42583?email_source=notifications&email_token=AADRH2244IYUD477CU3KBL3QDESVVA5CNFSM4IJJGJC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3UGLWA#issuecomment-518546904>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADRH26LCM5NABBDLIB4N2TQDESVVANCNFSM4IJJGJCQ> .