I seem to recall the Effect.Appear setting the final opacity to 0.99 to avoid some bug on some browser; anyone remember the specifics?  Seems like we should probably just conditionally check for the broken browser and set to 0.99 for only that one, otherwise leave it at 1.0, but I know I don’t have the full picture of why it was necessary or whether it still is.

 

Greg

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Javier Martinez
Sent: Monday, July 17, 2006 1:31 PM
To: rails-spinoffs@lists.rubyonrails.org
Subject: [Rails-spinoffs] scriptaculous appear effect and tiny_mce bug onopera 9

 

Opera 9 is available as a final version. Opera guys says that it's the first version compatible with WYSIWYG controls. I have tested Tiny_mce and works pretty well.
Only have found an error with scriptaculous opacity effects. When a hidden div with a tinymce control appear with the effect ( Effect.Appear ), tinymce is appear weird. There is some problem with opacity styles on tinymce. But these errors, only appear if the opacity has an intermediate value. A workaround to this is, after the Effect.Appear, set the opacity to 1 ( Element.setStyle( $( div ), {opacity:1} ) ). This seems to correct the problem... or I think...

PD: excuse me for my bad english
PD2: I don't know if this is the place to comment this... if not, excuse me again.

_______________________________________________
Rails-spinoffs mailing list
Rails-spinoffs@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs

Reply via email to