Opened 8 years ago

Closed 8 years ago

#7873 closed bug (cantfix)

Autocomplete: Autocomplete kills undo (ctrl+z) in IE 8

Reported by: sajad.mirzaei Owned by:
Priority: minor Milestone: 1.9.0
Component: ui.autocomplete Version: 1.8.16
Keywords: Cc:
Blocked by: Blocking:

Description

Ctrl+z does not work in fields which have autocomplete in IE 8. This issue has been tested on the autocomplete demo provided on the jqueryiu.com, too.

Change History (4)

comment:1 Changed 8 years ago by Scott González

Status: newopen
Summary: bug : Autocomplete : problem in IE 8 with undo (ctrl+z)Autocomplete: Autocomplete kills undo (ctrl+z) in IE 8

comment:2 Changed 8 years ago by tj.vantoll

This appears to be a bigger issue than IE8. See http://jsfiddle.net/aSs7s/2/. On my Windows Vista box, undo stops working as soon as you type something that causes the autocomplete options to display. This happens in IE9 as well as IE9 simulating IE8 and IE7.

While not quite the same, undo also doesn't work in Safari 5.1.2 after selecting an option from the autocomplete menu. I confirmed this on both Windows Vista as well as Mac OS X 10.7.2.

This does not appear to be an issue in Chrome 16, Firefox 9, and Opera 11.60.

comment:3 Changed 8 years ago by charansunkara

IE won't allow to perform ctrl+z(Undo) immediately after a DOM append or InnerHTML operation.

I guess this is the reason.

For example simply type any text that is not related to any items in the menu,Now do any operations like deleting the text using delete or back space key. CTRL+Z will work. But If you type any text that will show the menu, Now try deleting the text using delete or backspace key , Now try ctrl+z it will not work.

It's because when the text in the textarea or input matches with the list, We are appending the matched items to the menu and finally to the DOM . In this case IE breaks the CTRL+Z ie. undo

comment:4 Changed 8 years ago by Scott González

Resolution: cantfix
Status: openclosed

Confirmed that IE is killing undo after any DOM mutation. There's nothing we can do about this.

Note: See TracTickets for help on using tickets.