mich wrote:> Hello,
>
> I have a couple of rails applications, with a few AJAX''ified
features
> (visual effects, and auto_complete) - everything works smoothly (thanks
> for that...)
>
> I''ve tested the application in various browsers (opera, FF,
safari, IE
> etc etc) - and mostly things work as expected... now for my small
> problem - I have a number of users accessing the applications from
> citrix with an old version of IE (5.50) - and whenever there''s
some
> ajax visual effects on the page - the whole pages flickers and is
> general a pain to use..
It depends. If your site functions normally without these things and they are
just effects, then what I would do is pull out all of your JS from you markup
and put in into a Behaviour (http://bennolan.com/behaviour/) style external JS
file that applies all events, etc to your page. Then do some browser detection
on the server side to change which file is downloaded by those clients.
Something like this for Apache/mod_rewrite
RewriteCond %{HTTP_USER_AGENT} MSIE 5
RewriteRule ^/prototype.js$ /blank.js [L]
But as you get more and more hooked by Ajax, you''ll probably be
designing
interfaces that simply won''t work in older browsers. Then it would be
time to
upgrade.
--
Michael Peters
Developer
Plus Three, LP
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---