Search box in Discover is overridden by typeahead in Chrome 52

[wflyer]

Kibana version: 4.5.3

Server OS version: Debian Linux 8

Browser version: Chrome 52.0.2743.82 (64-bit)

Browser OS version: OS X El Capitan 10.11.5

Original install method (e.g. download page, yum, from source, etc.): Docker Hub imange 'kibana:4.5'

Description of the problem including expected versus actual behavior:
The search box in kibana Discover is overridden by typeahead lists.

In Chrome 51 (expected behavior)

In Chrome 52 (actual behavior)

Typeahead list overrides search box including search button. In the search input box, text value = "type: de" is written but not appeared.

Steps to reproduce:

1. Update Chrome to 52 in Mac
2. Enter Kibana and search something in dicover

Errors in browser console (if relevant): Nothing

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

[jbudz]

Confirming on 5.0 too, Chrome 51 is working.

[Bargs]

I've seen this as well, and it absolutely kills me.

[faelenor]

Same thing here. Not only that I can't see what I'm writing, but sometime when I try to edit the search string, the cursor disappears, the search bar becomes clickable and if I click it, it reloads the results. This is driving me crazy! That could be a Chrome bug though...

[Bargs]

@jbudz and I looked into this a bit and we can't figure out how this was ever working in the first place. As the code is written, Chrome seems to be working correctly whereas other browsers aren't. This is also broken in Chrome Canary, so it probably won't change back to the old behavior any time soon without a change on our end.

This is also a particularly nasty bug because it probably affects all versions of Kibana.

[w33ble]

It's been reported that this fixes the issue. I haven't tested it, and don't know if it breaks older version of Chrome, or other browsers though.

.typeahead .typeahead-items { 
  top: 32px; 
} 

[jbudz]

I just did a run through edge, ie11, chrome, firefox and it's looking good. Opening a PR shortly

[timander]

The search is completely unusable, I've been able to work around it by hitting ESC when it suggests the wrong history item (which is always).
Kibana Version 4.5.1 Build 9892 Commit SHA addb289
Chrome Version 52.0.2743.116 m

[wflyer]

@timander Recent release of kibana (v4.5.4) includes the merged PR and works well for me :)

[jbudz]

For anyone else running into this, this fix is in 5.0.0-alpha5, 4.1.11, and 4.5.4.

[dizzydis]

Is this actually fixed? I just updated to 4.5.4 and I seem to still be encountering the issue.

Kibana 4.5.4
Chrome: Version 52.0.2743.116 m

[Bargs]

Definitely fixed in 4.5.4. Need to clear browser cache maybe?

[dizzydis]

Tried a cache refresh, and tried in an Incognito window.. same results both times. Still getting the auto-complete/suggestion box covering up the typing section of the search bar.

[robert-7]

Hi @dayjavid, or anyone else, would you still be able to confirm if you're getting this issue on more recent versions of Kibana (4.5.4 or later)?

[ptherrien]

One other piece of the workaround/fix, adding "top: 32px;" didn't work for me until I moved the optimize/bundles directory to a different location before restarting the Kibana service. The directory will be recreated when the service starts back up. It takes a minute or two for all of the files to be recreated but once complete, the issue was resolved.

[dizzydis]

@robert-7 I am not experiencing this in 4.5.4 any longer.
I worked with someone on another thread and found my issue. I was doing an un-tar of the package on top of a running instance of Kibana. This led to the version number in the Settings of Kibana being updated to 4.5.4, but the bugs still existing.

To fix this, I tried both:

• Turning off Kibana before un-tarring.
• Backing up and removing the entire Kibana installation directory and re-creating it with a fresh deploy using the new version.

Both of these seem to have fixed the issue I was experiencing.

Thanks

[dugpa]

Issue exists on Chrome Version 53.0.2785.113 (64-bit) but works on Safari and Firefox and have cleared cookies and even reinstalled Chrome.

[Bargs]

@dugpa what version of kibana are you on? And did you try clearing all site data, not just cookies? I imagine there's a chance that reinstalling Chrome might not clear out your local caches, if they're stored separately from the chrome binaries themselves.

[stv-io]

I've also seen some weird / similar behaviour depending on whether I access kibana directly, or via an nginx proxy.

[edgahan]

We are using AWS Elasticsearch Kibana and I couldn't find a way to upgrade it... I ended up using the css fix above, #7801 (comment), but making it a chrome bookmark.

Steps:

1. Right click the bookmark menu and click "add page"
2. Enter "kibana-fix" as the name and as the URL put in:

javascript: document.getElementsByClassName("typeahead-items")[0].setAttribute("style", "top:32px");

Then whenever on kibana page with broken auto complete, press the bookmark.

[MCautreels]

For those that haven't upgraded yet or can't upgrade any time soon. We've build a very simple Chrome Extension that resolves the issue: https://chrome.google.com/webstore/detail/kibana-fixify/malbepndklhdndhmmfkbdchhmnbhnllg

[warroyo]

seeing this issue as well @MCautreels I am on version 53.0.2785.143 and this plugin doesnt seem to work.

[gitRahul]

I am seeing the exact same issue with Kibana v4.4.0 and Chrome: Version 54.0.2840.99 m

[robert-7]

Hey @gitRahul , so as mentioned above, Kibana v4.4.0 might experience this issue and should therefore be upgraded to v4.5.latest or later versions to fix it

[srinivasmangipudi]

I still see this very frustrating issue. Kibana-discover is so unusable with this problem.

[Shaidar20]

Still a problem in 4.5.2 (fresh install) and chrome (Version 53.0.2785.101). The previous search clobbers what i'm searching for.

[kjellericson]

I recomend the plugin Stylish: https://chrome.google.com/webstore/detail/stylish-custom-themes-for/fjnbnpbmkenffdnngjfgmeleoegfcffe

Then you can easily use the css that w33ble recomended. It took me 20 seconds.

[spydesk]

Have the same problem with version 4.5.3 and Firefox 52.0.

I was using Firefox instead of Chrome as a workaround to this problem.

[kolka10]

Same issue ( spend 2 days to reconfiguration of ELK stack)
Chrome: Version 57.0.2987.110 (64-bit)
Kibana: Version 4.5.3 Build 9910

Switched to FireFox as well

[Windowsfreak]

@spydesk @kolka10 @Shaidar20 Just update to 4.5.4 to fix it

[fureweb-com]

Please install this chrome extension.
You can avoid that bug.

https://chrome.google.com/webstore/detail/chrome-extension-for-kiba/almhdllkjoojdmklbdhdfjgkkkimkgjk

[kolka10]

Yes - Already found it - thanks !!!

…

On Thu, Jul 19, 2018 at 2:05 PM, Jihwan Oh ***@***.***> wrote: Please install this chrome extension. You can avoid that bug. https://chrome.google.com/webstore/detail/chrome-extension-for-kiba/ almhdllkjoojdmklbdhdfjgkkkimkgjk — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#7801 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AZea_D4l3HGF1vasH47Rd7U_kyOSrb8cks5uIGgNgaJpZM4JSiy7> .