Skip to main content

Search and Top Navigation

#9796 closed bug (wontfix)

Opened February 07, 2014 12:50PM UTC

Closed April 17, 2017 08:28PM UTC

Autocomplete: Search triggered on initialization if input contains an umlaute

Reported by: Mil Owned by:
Priority: minor Milestone: none
Component: ui.autocomplete Version: 1.10.4
Keywords: Cc:
Blocked by: Blocking:


I have a very odd issue with autocomplete, IE10 and jquery-ui version 1.10.4 (also occures in version 1.9.0).

If I add a value with umlaut (ö, ä, ü) as initial value in the input with autocomplete, autocomplete gets triggered while loading the document.

Please look here and play run.

I could only see that behaviour in IE10 (10.0.9200.16466), older versions and compatibility mode seem to be fine. Maybe there is a localization option I miss?

Thanks in advance


Attachments (0)
Change History (8)

Changed February 07, 2014 02:27PM UTC by scottgonzalez comment:1

status: newopen
summary: Autocomplete with umlaute in valueAutocomplete: Search triggered on initialization if input contains an umlaute

I'm not sure if we'll be able to do anything about this. IE is triggering an input event.

Changed April 03, 2014 06:49PM UTC by scottgonzalez comment:2

I've reported this to Microsoft to see if they have any suggestions to work around this. Here's a reduced test case without jQuery:

Changed April 03, 2014 07:02PM UTC by Mil comment:3

I did too. Shortly after you stated that this is a browser issue. Last message was, that they will look into it.

Changed September 29, 2015 08:42AM UTC by nicoder5 comment:4


I was faced the same bug and found a workaround here that seems to work :

 		input: function( event ) {
-				if ( suppressInput ) {
+				if ( suppressInput || typeof suppressInput === 'undefined' ) {
 				suppressInput = false;
 			this._searchTimeout( event );

Has this been proposed / discussed already ? Is it a good idea ?



Changed March 01, 2016 02:04PM UTC by scottgonzalez comment:5

#14924 is a duplicate of this ticket.

Changed March 01, 2016 02:04PM UTC by scottgonzalez comment:6

#14925 is a duplicate of this ticket.

Changed April 05, 2016 10:34AM UTC by MilKAOS comment:7

Hi all

Good news everyone. Microsoft took my bug yesterday from Connect to their platform for IE Edge issues/feature requests and set the status for the bug to Fixed.

See here:


Changed April 17, 2017 08:28PM UTC by scottgonzalez comment:8

resolution: → wontfix
status: openclosed

This doesn't seem to affect Edge and we don't have a fix for IE, so I'm going to close.