#150 new
Frank Burleigh

Raising Effect.Opacity on a P with first-line bold rule depresses IE7

Reported by Frank Burleigh | December 31st, 2008 @ 06:46 AM

Let's talk about an edge case. ;-) Through some hours horsing around with IE7 I've learned that this bit of scripting:

new Effect.Opacity(aStageElt, { from: 0.0,to: 1.0,duration: 1.0} );

run on a P element whose first-line is styled this way:

stagebox p#stage:first-line {

font-weight:bold;

}

knocks IE7 into the next solar system. WinXP doesn't quite call IE7's mood "not responding" but nonetheless IE7 has in fact stopped responding.

Details: prototype 1.6.0.3 and script* 1.8.2.

It's hard to say why this is your "bug" but I'm not sure where else I'd put it. I've also extracted my use into a reduced case (remove the commenting around the above style rule to see IE7 sleep) but have left enough of what I was doing intact so you can compare Firefox 3.x and Safari with the IE7 behavior.

Changing the direction does alter that behavior. To get IE7 to be bad, the snip must go from less to more opacity.

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