Change in dialog(?) between Jquery UI 1.10 and 1.11 triggers noneditable textboxes in IE 11
We recently upgraded from 1.10.3 to 1.11.4 and that upgrade apparently triggered an error in IE11.
We use JQuery UI dialogs (dynamically generated div including an iframe) to display pages that basically a lot of info as tabular data. We have an asp.net webcontrol tree on the left and an iframe to display a webforms page for the currently edited record
In the dialog you can select one record and trigger the loading of the record down on the "normal" page. The dialog gets .destroy -ed and the dynamically generated div gets removed from dom, data from the dialog gets sent to the "regular" iframe on the page
We have some pages where different kinds of records get loaded to make a new record, so multiple dialogs are opened. If we do this, all is fine after we press save (which normally triggers going from the "regular" iframe on the page to the navigation on the left, clearing the iframe(whose source has been set via javascript and gets set back to nothing on postback) and changing the src to the page where the next record is displayed.
If we just select one record from the dialog and then press save after the upgrade, the next time we open the dialog you can't enter any text in the text boxes in the page that is displayed in the iframe in the dialog. The textbox apparently get focus (as the borders are displayed differently after a click), but you are unable to enter anything. The funny thing is that if you then press tab a few times and get back to this textbox it suddenly works.And stays that way.
Downgrading to the 1.10.4 fixes this error consistently. I looked through the changelogs and found some fixes that relate to memleak fixes. Could it be that we actually happened to benefit from one of those menleaks and the way IE11 handles iframes?
Sadly I can't pinpoint it to one single change as jquery ui has been restructured between 1.10 and 1.11.
We use JQuery UI dialogs (dynamically generated div including an iframe) to display pages that basically a lot of info as tabular data. We have an asp.net webcontrol tree on the left and an iframe to display a webforms page for the currently edited record
In the dialog you can select one record and trigger the loading of the record down on the "normal" page. The dialog gets .destroy -ed and the dynamically generated div gets removed from dom, data from the dialog gets sent to the "regular" iframe on the page
We have some pages where different kinds of records get loaded to make a new record, so multiple dialogs are opened. If we do this, all is fine after we press save (which normally triggers going from the "regular" iframe on the page to the navigation on the left, clearing the iframe(whose source has been set via javascript and gets set back to nothing on postback) and changing the src to the page where the next record is displayed.
If we just select one record from the dialog and then press save after the upgrade, the next time we open the dialog you can't enter any text in the text boxes in the page that is displayed in the iframe in the dialog. The textbox apparently get focus (as the borders are displayed differently after a click), but you are unable to enter anything. The funny thing is that if you then press tab a few times and get back to this textbox it suddenly works.And stays that way.
Downgrading to the 1.10.4 fixes this error consistently. I looked through the changelogs and found some fixes that relate to memleak fixes. Could it be that we actually happened to benefit from one of those menleaks and the way IE11 handles iframes?
Sadly I can't pinpoint it to one single change as jquery ui has been restructured between 1.10 and 1.11.
Topic Participants
jonasbnschmidt
jakecigar