Well... ok.. Mozilla based browsers. But that is far from being only Firefox (Mozilla, Camino, Flock, Netscape, etc.). It is indeed deprecated, but you know how that goes... how long has the font tag been deprecated, but browsers will continue supporting it for the foreseeable future. I'm sure that eval as an inherited function from Object will go away sooner than <font>, but that doesn't mean that it won't break code for a whole lot of users now.
On 11/22/06, Klaus Hartl <[EMAIL PROTECTED]> wrote: > Paul McLanahan schrieb: > > In most modern browsers (IE Excluded of course), the built in eval > > function is defined on all objects. This is designed to combat the > > problem we're trying to fix now, which is that you can eval code in > > specific context (in FF for examle) by just calling > > myObj.eval(codeString);. > > > You are talking of "most modern browsers". As far as I know, the eval is > only implemented in that way in Firefox (which is far from being most > modern browsers). > > Plus according to the Mozilla Doc it is deprecated: > http://developer.mozilla.org/en/docs/Core_JavaScript_1.5_Reference:Global_Objects:Object:eval > > More here: > http://my.opera.com/hallvors/blog/show.dml/449976 > > -- > Klaus > > _______________________________________________ > jQuery mailing list > [email protected] > http://jquery.com/discuss/ > _______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
