They are located under Prototype to incurage you to NOT use/depend/rely on
them. You should generally not write code that tests for which browser it runs
in - it's a job for Prototype et al. to add an abstraction layer.
Fra: firstname.lastname@example.org [mailto:[EMAIL PROTECTED] På vegne af
Sendt: 7. juni 2007 09:01
Emne: [Prototype-core] Re: Browser-Class
well, I would prefer something like a new Browser Class. So We could use
These do not really belong to "Prototype". Further we could move
BrowserFeatures to Browser.feature.
Then we could implement
What do you think?
Tobie Langel schrieb:
> Hi Freddy,
> There's a ticket in tract for that already.
> the main thing that has been delaying it's implementation is finding
> the right names for these mrthods, so any suggestion is welcomed.
> On Jun 6, 6:14 pm, Freddy <[EMAIL PROTECTED]> wrote:
>> Hi Guys,
>> as far as i know there is no possibility to calculate the size of
>> browserwindow with prototype yet. But this could be very useful to
>> place e.g. a div-popup in the middle of the window.
>> I always use my own functions. If you also see a common need I would
>> create a sample patch to include it in prototype. What do you think,
>> is this useful or to specialized?
Frederic Gaus pgp-key: 93E6903C
fingerprint: 0C55 4517 CC1E 5F7F 9059 3535 AB54 D8E8 93E6 903C
You received this message because you are subscribed to the Google Groups
"Prototype: Core" group.
To post to this group, send email to email@example.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at