"check to see if prototype already has a wrapper for what you're trying to accomplish."
And of course, if not, consider writing a wrapper and submitting it to Prototype for inclusion. On Jun 24, 4:07 pm, "Jerod Venema" <[EMAIL PROTECTED]> wrote: > There are some very rare cases where browser detection is the only way to > deal with particular issues. But prototype is designed so WE (ie, the web > developer) don't have to deal with those rare cases. > > If you think you have no way of avoiding browser sniffing, check to see if > prototype already has a wrapper for what you're trying to accomplish. > > -Jerod > > On 6/24/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > > Ah, that explains the lack of documentation and features. And makes > > perfect sense. Thanks for the info Kroc. > > > I'm really impressed that so many people onlist are successful in > > completely avoiding browser detection. Even the guys who started this whole > > Rails things (37 Signals) do it as do the guys who started Scriptaculous > > (Thomas Fuchs at wollzelle) resort to sniffing in some cases. I guess I > > ought to up my game, so to speak. > > > -jack --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
