> Could this somehow be reported to the authors of these libraries that
> practice this bad habit?
> jQuery could be modified, but sacrificing performance just for one or two
> scripts that do this seems detrimental (especially if it affects very few
> users).
>
> Maybe there should be a list of libraries that do this, stating that they
> are incompatible with jQuery (and I expect other libraries as well)?
>
> ViaMichelin have a developer blog, so I expect that this can be reported to
> them (and maybe someone who can figure out the API can suggest a fix)?
> http://dev-blog.viamichelin.com/
>
> They also have a developer network:
> http://dev.viamichelin.com/
>
> 2008/6/4 John Resig <jeresig@...>:
>>
>> > It seems to indicate that jQuery assumes that no properties have been
>> > added to Object.prototype?
>> > Is it possible that jQuery should be using hasOwnProperty in "for ...
>> > in" loops?
>>
>> That is certainly an option - but at the cost of performance. We've
>> done testing of this in the past and have, for now, opted to err on
>> the side of performance instead of ubiquitous compatibility. We may
>> change this eventually but that's our reasoning, for now.
>>
>> --John
>>
>>
>
>
> >
>