Hi ryanm,
I see what you are saying about the object node existing in the dom tree
in IE's (or any browser's) memory, even if the object is set to
display:none. I think the question as it relates to this hack is whether
in IE's specific implementation is downloading and running the
ActiveXObject if the object is hidden in this way.
There are some ways to test this, as some other on here have done with
promising results (and I'll add my own tests in a few), but it would be
good to get a hold of some documentation that show's clearly whether or
not IE is loading that content.
Kevin N.
ryanm wrote:
Following my previous email, I thought of a better way to test
display:none
with flash.
Display:none causes the object not to be rendered, but it is still
instantiated in memory. The object exists and will begin loading, but
but will not be displayed or consume any real estate on the page. The
visibility style doesn't affect how the element is rendered, it only
affects whether it is visible or not, so an invisible elemnt still
takes up real estate on the page, you just can't see it. So if you
have a table with display:inline that is invisible, the space will be
reserved for the table, but it will not be rendered to the page. The
display style sets the display mode of the element (inline, block, or
none), and determines how page space is reserved for the element. It
does not, however, tell the element anything at all about whether to
begin loading, elements will load according to their defined behavior
as soon as they exist on the page.
ryanm
_______________________________________________
[email protected]
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
