#192 new
Daniela

BlindDown IE6 and swfobject

Reported by Daniela | April 12th, 2009 @ 02:50 AM

I put

    style="display:none;">

and Effect.BlindDown for "page" element

everything works beautifully in all browsers and for everything contained in that page, EXCEPT

in IE6 for the following situation:

Nested in the "page"div is a swfobject (dynamic publishing). This object is just a tiny empty animation that loads the real animation when the user clicks a button to request it. The object does display, but the second .swf file that is loaded by the original one, does not display - it is loaded though, it does the expected "actions". If I remove the "display:none" bit, it works ok.

This problem only appears in IE6, not in IE7, Safari, Chrome or FF. The page is more elegant if it starts set to "display:none" (you suggest this in the wiki), but it fails in IE6

thanks, Daniela

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

script.aculo.us is an open-source JavaScript framework for visual effects and interface behaviours.
<br/><b>Source available from github</b>
The Git repository resides at:
<a href="http://github.com/madrobby/scriptaculous">http://github.com/madrobby/scriptaculous</a>
<br/>Check out the current development trunk with:
<code>git clone git://github.com/madrobby/scriptaculous.git</code>
<br/>As <b>script.aculo.us 1.xx is feature-frozen</b>, this development trunk is for <b>bugfixes only</b>.
<br/>New development should happen only for
<b>script.aculo.us 2</b>.
<br/><b>Creating a bug report</b>
When creating a bug report, be sure to include as much relevant information as possible. Post a an example that shows off the problem. Preferably, <b>alter the unit tests</b> and show through either changed or added tests how the expected behavior is not occuring.

People watching this ticket

Attachments

Pages