I second Andrew. Centralizing all the browser related features in the
Prototype Namespace seems a good idea as we already started doing this
with "Prototype.BrowserFeature".

We could also add a "Prototype.Browser.isSupported" Boolean property
which would only return true for the browsers officialy supported by
Prototype.

Tobie


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Prototype: Core" 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/prototype-core?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to