Maybe run an invisble but expensive animation and check how many steps are actually rendered, eg. animate an element for 100px for 100ms and check how often the step-callback is actually called for that animation. Anything below a certain threshold is considered too slow.
Jörn On Tue, Oct 7, 2008 at 8:07 PM, John Resig <[EMAIL PROTECTED]> wrote: > > How would you detect if someone is on a slower machine? (Just curious) > > But yes, it was discussed recently that passing in an animation speed > of 0 might have that effect. Another good side effect is that > animations can be disabled for accessibility reasons (e.g. people who > have extreme motion sickness). > > --John > > > > On Tue, Oct 7, 2008 at 11:00 AM, Florin <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >> Animations and special effects (like fadeIn/fadeOut) are very nice, >> but on slower computers they don't look so good and are a serious >> performance issue. >> >> Would you consider an option to disable the animations? >> >> For instance, any call to animate() would just set the corresponding >> final CSS and call the callback, without animating through the >> intermediate steps ? >> >> Any workarounds which don't require changing the code a lot ? >> >> >> >> >> >> >> > >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
