Kibana: Cannot backspace search-string

[thomasneirynck]

I witnessed this on Chrome 52/OSX

• type in a search string in the query bar of the Discover page
• results are loading
• try to backspace the searchstring.

-> the string cannot be deleted. It is as if the typeahead keeps refilling in the previous string.

This did not occur on Firefox on the same machine.

[rashidkpc]

Dupe of https://github.com/elastic/kibana/issues/8027

[epixa]

@thomasneirynck What version of Kibana did you see this in? The linked ticket above was apparently fixed in 4.5.4

[thomasneirynck]

@epixa 4.5.4 (hosted on Elastic cloud)

it does look similar to #8027 though

[epixa]

In that case I'm going to reopen this until we can track it down. The issue in linked ticket was definitely fixed in 4.5.4

[thomasneirynck]

could be reproduced on alpha4 as well.

[bahaaldine]

Same issue happens to me on Chrome Version 53.0.2785.101 (64-bit) and Kibana alpha4

In the following GIF, you can't really see it, but I'm hitting the backspace button to remove "cold play" from the search bar, after the search is completed

[rcompton]

Chrome 52.0.2743.116 same problem. Would be nice to have an option that disables all autocomplete.

[https://discuss.elastic.co/t/stop-delete-key-from-bringing-up-autocomplete/61167]

[thomasneirynck]

duplicated by #8507. Description reposted here:

Several issues here:
1) When I try to focus the input field, hitting backspace seems to unfocus it. This makes changing my text almost impossible. As a workaround I had to select the text, and hit backspace.

2) When I start typing, if there are autocomplete options, the cursor indicator vanishes. This makes it impossible to see where I am typing. Very frustrating.

3) As I start typing in the input, Kibana seems to fire off another query prematurely. This results in "query already running" errors. I'd prefer to have a "submit" button instead of auto-submit as I

[kobelb]

I'm currently unable to duplicate this.

@jbudz I know that you fixed a linked issue in 4.5.4, could this have also been occurring in 5.0.0-alpha4 and been fixed also?

[jbudz]

@kobelb yes, the fix landed in alpha5.

[kobelb]

@epixa you comfortable with us closing this and marking it as a duplicate?

[epixa]

@kobelb My concern is that this issue was _reported_ in 4.5.4, though the original issue was suppose to be _fixed_ in 4.5.4.

[kobelb]

@epixa cool, I'll leave it open then, and wait until we have repro steps.

[Kenterfie]

+1 the problem makes kibana usable for me

[kobelb]

@Kenterfie would you mind verifying the version of kibana that you're running? Also, has this instance been upgraded, another user reported that their upgrade procedure had to be altered to get this fix: https://github.com/elastic/kibana/issues/7801#issuecomment-245735524

[Kenterfie]

@kobelb thanks for your advise. I have checked everything and upgraded now the kibana instance with success. The repository i have used was not current.

[kobelb]

@Kenterfie glad to hear that fixed your issue! Thanks for getting back to me.

[tbragin]

Closing since we haven't seen new activity on this. Per @epixa this should have been fixed in 4.5.4 https://github.com/elastic/kibana/issues/8306#issuecomment-252959719

[liubhub]

I have this issue using Kibana 4.5.2 on Chromium(68.0.3440.106 version), Ubuntu 16.04, also the same thing in mozilla 62. I can't change my search input. Are there any workarounds without having to upgrade Kibana?