Kibana: Dashboard Filter autocomplete off

@becker-IT if you click out of the input box, does the autocomplete go away?

Nope, I click

Dashboard
Open saved Dashboard
Type for example "A" in the input field

and the result is I can't target the saved dashboards because the browser history is in front. When I click again in the input field the browser history is loading again.

Hit escape and the autocomplete will dismiss

Ah I see, what a perfect solution!
I prefer this one: autocomplete="off"

@becker-IT where did you set that?

This option is awful. I have to hit escape after ever letter I delete... HATE it

It would be fine if

1. the focus did not switch from typing to the autocomplete,
2. the autocomplete would appear BELOW the bar.

otherwise like @kevin-m-rego mentioned, modifying queries from previous completes (say i want to change a few things on the end, like a port number) is worse than dueling with chrome autocomplete.

That autocomplete thing is very annoying, I suppose it's status is "feature, not a bug"?

I completely agree with @hollowimage. With these 2 improvements I would be totally fine but right now it's basically unusable if you don't have 5 minutes to change one query...

I'm not sure I understand the problem. Are you having trouble with the browser's autocomplete, or Kibana's autocomplete? Which version of Kibana? And what's happening exactly? Some screenshots or a gif would be great.

@Bargs it seems that the browser's autocomplete is messing with the input field. I managed to reproduce the problem, but on the discover page though. I hope nonetheless this is useful:

This was tested on:

• Kibana 4.5.3 (I can try with latest if you want, I just happened to be working with that version)
• Chrome Version 52.0.2743.116 (64-bit)

The browser autocompletion seems to be (nearly) always on the way. You can see that the "lense" icon on the right disappears when this is the case.

@scampi that issue was fixed in 4.5.4.

@MaxBosse is this the same issue you're seeing?

Yes it is the same issue I was seeing, I will make sure we are updating to the latest version, thanks @Bargs :+1:

@Bargs updating to 4.5.4 helped, thanks a lot

Was this issue fixed in the 4.1.x branch (for older Elasticsearch versions) as well? And if yes, which version?

@ikoniaris fixed in 4.1.11

For anyone affected from this aggravating issue there's a quick way to get rid of the suggestion box to regain control over what you type.

Admittedly not the ideal solution, but it works in an environment where you can't afford to update Kibana to fix a trivial UI issue.

The workaround consists in removing the change, focus, and keydown event listeners through the Chrome Inspector (Inspect element searchSource, then from the CSS pane go to Event Listeners to find the listeners to unbind) so that you can type freely in the search bar.

What version of Kibana can I use with ES to implement the fix or are there no compatible versions of Kibana with the fix that are compatible with ES version v1.5? I see the 4.1.x versions fix the issue, but are those compat. with v1.5 of ES? Thanks!

I got so fed up with this 'feature' today on 4.1.x that I whipped up a little grease/violet/whatever monkey script to deal with it

// ==UserScript==
// @name Kibana autocomplete killer
// @namespace kibana
// @grant none
// @include https://<your kibana site>/*
// ==/UserScript==

function main() {
  document.addEventListener('click', function() {
    var jq = window.jQuery

    var searchbox = jq('.input-group input')
    searchbox.unbind("change");
    searchbox.unbind("focus");
    searchbox.unbind("keydown");

    console.log("removed");
  });
};

var script = document.createElement("script");
script.textContent = "(" + main.toString() + ")();";
document.body.appendChild(script);

thanks for @SleepyBrett 's script ,it works well for me.

Thanks @SleepyBrett.

FWIW I have found a much simpler CSS workaround (source: Kibana issue #7801) which works very well but it needs an extension like Stylish or Stylebot.

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