Using some more basic YUI components (I actually like their simple pieces a lot better than the complex components, as skinning them is a bit of an undertaking if you don’t want them to look YUI-like), I whipped up the two easiest examples of this I could think of: a 2×2 pane and a 4×1 pane:

Another oddity: one of the “popup” dialogs displayed a history of changes. Because this was the piece of data I’ve been using to test for the last few weeks, there was a LOOOT of history (scroll-bars, coming soon to a page near you). When the dialogs opened for the first time, the page would grow to accommodate the new dialog. When the dialogs closed, though, the page would remain “stretched out.” Which means that somewhere in the YUI code, they’re not actually removing the content when you close the dialog–they’re merely obfuscating the contents somehow. Rather than read through several hundred lines of YUI javascript, I did a test.

The YUI dialogs make use of a div with an id of “hd” for the header and “bd” for they body. The header is only a line, so it wasn’t worth fussing with. Using the YUI custom event model, I added some code to listen for the cancel/submit/hide calls and take the extra step of setting the “bd” div’s CSS style to “display:none”. Blammo. Everything works fine. The page shrinks back down to its proper proportion and–wonder of wonders–the SWF div stays visible and on top.