On 11/2/11 11:52 PM, Michael A. Puls II wrote:
If we want to keep the display: none behavior that's in current browsers, I'm not going to object. Just saying that it'd be nice (better/make more sense) if the use-case for display: none (deferring instantiation till it's shown) was handled by an attribute (instead of css) where removing the attribute made it come alive. That should be compatible with older browsers for sites already using display: none for deferring instantiation
I think having an explicit instantiation trigger that works even if display:none would be a reasonable thing to do.
-Boris
