> It would be nice to allow clicks & presses ONLY if originating from > within the modal window. Perhaps this could be accomplished by examining > focus & parent? Would this block users from typing in the browser's > address bar? The goal would be to allow a form within a modal window to > be populated & submitted using keyboard or mouse, and to block > everything outside of the *currently active* modal. > > I don't think it will be possible to prevent the user from using tabs > to access links and inputs/buttons in the background page, but the block > code should intercept the call (<enter>, key press) to execute or > populate these links/inputs.
Bruce, Good points. You're right of course, key/mouse events should only be blocked for the underlying content. I'll try to fix that in blockUI (I found another bug in there too, so thanks for making me take another look at it.) Another good resource to look at is Gavin's modalContent plugin. Looks like his demo page isn't working right now but he did a good job on that code and has some cool animation support. Remember that you can use 'z-index' in a call to jQuery's css method. :-) Regarding opacity in Opera, it's fully supported in Opera 9. Did you try applying it to the IFrame? Another nice feature to add would be to focus the first visible input in the modal content. Even better would be to restore the previously focused element when the modal dialog is dismissed, but I'm not sure how to do that. Keep up the good work. Mike _______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
