#4309 closed bug (fixed)
Opening multiple modal dialogs causes access problems to inputs
Reported by: | boconnor | Owned by: | Scott González |
---|---|---|---|
Priority: | blocker | Milestone: | 1.7.2 |
Component: | ui.dialog | Version: | 1.7 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
A modal dialog (Dialog A) is opened that has an <input> field. Another modal dialog (Dialog B) is opened. Modal Dialog B is closed.
It is now impossible to focus on the <input> field in Modal Dialog A.
Bug exists on all browsers.
Attachments (3)
Change History (13)
Changed 14 years ago by
comment:1 Changed 14 years ago by
This has something to do with the events being added to modals. If you remove the event list from line ( link to code ) it works. Of course, this also breaks other functionality. I haven't determined if it's related to when they are binded or when they are unbinded. If there are any events in there, this problem persists. I tried removing each individual one. Didn't help.
comment:2 Changed 14 years ago by
Removing the if expression from this code block also makes it so it works:
destroy: function($el) { this.instances.splice($.inArray(this.instances, $el), 1); if (this.instances.length === 0) { $([document, window]).unbind('.dialog-overlay'); } $el.remove(); }
I think this would break all the overriding event binds from the original dialog box though. It looks like it should unbind all the .dialog-overlay events for the first dialog or previous dialog box if more than 2.
Changed 14 years ago by
Attachment: | jquery-ui-dialog.patch added |
---|
patch file for jquery-ui.js version 1.7.1
comment:3 Changed 14 years ago by
The patch file I put in there is the current patch file we are going to use to get around this until a better solution becomes available. Hopefully it might help in coming up with a more permanent solution in the core.
comment:4 Changed 14 years ago by
Milestone: | TBD → 1.8 |
---|
comment:5 Changed 14 years ago by
Owner: | set to scott.gonzalez |
---|---|
Status: | new → accepted |
comment:7 Changed 14 years ago by
Milestone: | 1.8 → 1.7.2 |
---|
comment:10 Changed 13 years ago by
I ran into this problem despite the fixes because I had another element in the page using the ui-dialog class (an older piece of the page was using jqModal, and we updated it to look like ui-dialog by just putting the class on the DIV). As a result, because this element did not have a z-index, when the line of code that checks the z-index was run, the value of z-index was "auto". This causes maxZ to be evaluated as NaN, and causes the problem described above. I was able to fix the problem by ensuring this other element had a numerical z-index.
Simple example of problem