What about when the feature is implemented, just not correctly? Do you think Prototype.Browser.whatever should be removed from prototype.js? I personally find it quite handy for those situations when nothing else seems to work and deadlines are looming.
I (probably like most of the people on this list) hate browser detection. If nothing else it isn't future proof. And who wants to code web pages for Microsoft products when, after all, we really want to code towards standards so that they can become more accepted and be advanced. But when it comes down to a decision between spending several hours coding something "the right way" and coding something in a few minutes that works for 97+ percent of the web.... I find myself in a grey area where perfect conformance to standards seems unrealistic or at least inefficient. That said, I agree with you Rob. I just don't think its pragmatic in every single situation. On 6/23/07, RobG <[EMAIL PROTECTED]> wrote: > > > > > On Jun 23, 12:36 am, [EMAIL PROTECTED] wrote: > > I find the Prototype.Browser methods so useful that I made two more that > > others might find helpful: > > Browser detection is a seriously flawed strategy for writing cross- > browser scripts, just don't do it. Use feature detection. > > > -- > Rob > > > > > -- [EMAIL PROTECTED] & thoughtbucket.tumblr.com] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
