Just wanted to give everyone a heads up with a quick and dirty fix.
Version 1 of iBox was modal. It is called a "lightbox" and perhaps not
really meant to be modal... but it was, and worked great. Version 2 of
iBox goes to great lengths *not* to be modal. If you run through the
"ibox.js" file searching for "click" you can comment out the lines that
register "hide" handlers whenever you click on areas such as the overlay
(the dark region).
I guess, for the uses that "iBegin" has for their iBox framework, the
change makes sense. They don't refer to their iBox as "modal". As far as I
know, this change is not documented anywhere but here, now, in this
listserv. Us WOrriors, however, noticed it was modal, and even wrapped it
with a component named "AjaxModalContainer". So it came as a shock to
realize that it no longer behaves in a modal manner at all.
To recap -> Just eliminate the lines that register "hide" everywhere you
find a "click" in "ibox.js"
Oh, and one more semi-related thing - Cheers for Anjo for tweaking the
"keypress" event to being a "keyup" event to detect the "escape" key in
Safari. On the other hand, my ears perked up when I noticed that it is
listening for this event at the entire "window" level... this could cause
cross polination issues if you have other plans for the escape key on your
page... Just something to be aware of. I commented that line out just
because our users don't need to hit "escape" to close the modal dialog,
and we might want to put some other like auto-completer widget inside the
modal dialog that would hide the auto-complete menu when you hit "escape"
rather than just close the whole dialog.
Get latest updates about Open Source Projects, Conferences and News.