These techniques touch on something I’ve been recently puzzling over; script.aculo.us effects require that elements which are hidden/shown using so-called ‘combination effects’ that are supposed to be initially hidden cannot be hidden using a stylesheet but instead only through inline styles (I’m not sure what the exact technical reasons for this are, but sure enough if you use a stylesheet to hide them, they’ll never be shown via scriptaculous). My solution was to add an onLoad event method which manually hid all qualifying elements. The problem there is, as you say; the equivalent of a FOUC – the elements are there as the page loads, but disappear as soon as loading finishes. Really they should be hidden immediately.
Perhaps there’s something in your tips above that might work here…
Ben Darlow
These techniques touch on something I’ve been recently puzzling over; script.aculo.us effects require that elements which are hidden/shown using so-called ‘combination effects’ that are supposed to be initially hidden cannot be hidden using a stylesheet but instead only through inline styles (I’m not sure what the exact technical reasons for this are, but sure enough if you use a stylesheet to hide them, they’ll never be shown via scriptaculous). My solution was to add an onLoad event method which manually hid all qualifying elements. The problem there is, as you say; the equivalent of a FOUC – the elements are there as the page loads, but disappear as soon as loading finishes. Really they should be hidden immediately.
Perhaps there’s something in your tips above that might work here…