I believe it was either in the changelog or some file in the Prototype source that discussed the reasoning behind the Prototype.Browser. It's used solely to reduce code complexity and increase code readaibility inside Prototype for the hacks they have to implement. They do the hacking, so that you don't have to. Prototype is designed to make the same functions work the same across all supported browsers. Its for this reasoning that Protoype.Browser is basic, nor documented on the API.
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
