Tench
2005-Jul-27 07:58 UTC
[Rails-spinoffs] safari vs. firefox on mac os x: flickering combination effects
Hi. I''m wondering if this is a documented problem. Combination effects such as .BlindDown or .SlideDown exhibit a not so fun flicker at the end of their rendering process in Firefox on Mac OS X. This does NOT happen in Safari. Does anybody know how to fix this or if it will get fixed in a next release? All best, Tench
Andrew Kaspick
2005-Jul-27 10:23 UTC
[Rails-spinoffs] safari vs. firefox on mac os x: flickering combination effects
There''s flickering in IE as well for those. A fix (at least for IE) was proposed on this mailiing list before, but I''m not sure if it has been or if there are plans to incorporate it into the next release. If you search back in the mailing list for messages with the subject ''flashing divs in IE with use of BlindUp and BlindDown'', you''ll find the proposed solution. Not sure if this fixes the issues you''re seeing in the other browsers as well though. On 7/27/05, Tench <psychomachine@mac.com> wrote:> Hi. > > I''m wondering if this is a documented problem. Combination effects > such as .BlindDown or .SlideDown exhibit a not so fun flicker at the > end of their rendering process in Firefox on Mac OS X. This does NOT > happen in Safari. > > Does anybody know how to fix this or if it will get fixed in a next > release? > > All best, > Tench > _______________________________________________ > Rails-spinoffs mailing list > Rails-spinoffs@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs >
Tench
2005-Jul-27 10:59 UTC
[Rails-spinoffs] safari vs. firefox on mac os x: flickering combination effects
Thanks a lot, Andrew, for your response. Unfortunately, the IE fix doesn''t change anything in the way Firefox on OS X renders these effects. Does anybody know if the problem I am seeing occurs on Macs only, or if all flavors of Firefox flash at the end of BlindDown? Tench On 27. ??? 2005., at 15:56, Andrew Kaspick wrote:> If you search back in the mailing list for messages with the subject > ''flashing divs in IE with use of BlindUp and BlindDown'', you''ll find > the proposed solution. > > On 7/27/05, Tench <psychomachine@mac.com> wrote:>> Combination effects such as .BlindDown or .SlideDown exhibit a >> not so fun flicker at the >> end of their rendering process in Firefox on Mac OS X. This does NOT >> happen in Safari.
Thomas Fuchs
2005-Jul-27 11:20 UTC
[Rails-spinoffs] safari vs. firefox on mac os x: flickering combination effects
That''s a firefox bug. Giving the outer DIV elements "overflow:hidden" should fix this (note I "think" the FF bug is fixed with the upcoming Firefox version 1.5). You''ll also need the 1.1beta script.aculo.us version or later (as far i remember). :) Thomas Am 27.07.2005 um 16:32 schrieb Tench:> Thanks a lot, Andrew, for your response. Unfortunately, the IE fix > doesn''t change anything in the way Firefox on OS X renders these > effects. > > Does anybody know if the problem I am seeing occurs on Macs only, > or if all flavors of Firefox flash at the end of BlindDown? > > Tench > > On 27. ??? 2005., at 15:56, Andrew Kaspick wrote: > > >> If you search back in the mailing list for messages with the subject >> ''flashing divs in IE with use of BlindUp and BlindDown'', you''ll find >> the proposed solution. >> >> On 7/27/05, Tench <psychomachine@mac.com> wrote: >> > > >>> Combination effects such as .BlindDown or .SlideDown exhibit a >>> not so fun flicker at the >>> end of their rendering process in Firefox on Mac OS X. This does >>> NOT >>> happen in Safari. >>> > > _______________________________________________ > Rails-spinoffs mailing list > Rails-spinoffs@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs >
Tench
2005-Jul-27 11:26 UTC
[Rails-spinoffs] safari vs. firefox on mac os x: flickering combination effects
Thanks a lot, Thomas. Yes, "overflow:hidden" does the trick. On 27. ??? 2005., at 16:53, Thomas Fuchs wrote:> Giving the outer DIV elements "overflow:hidden" should fix this > (note I "think" the FF bug is fixed with the upcoming Firefox > version 1.5).