One idea would be to write a compatibility check script
"jquery-compatibility.js" that collects and stores the experience
gained from debugging such compatibility issues in the form of
JavaScript code. (If I recall, in a separate thread, a version of
prototype was found incompatible because it changed Array.prototype in
some way).

This script, when included in the place at which otherwise jquery.js
would be included, could check the environment for such conditions as
whether properties have been added to the prototype of essential
objects by already included scripts. It could also contain specific
checks for properties added by libraries known to be incompatible.
Since much JavaScript code is copied between sites, the same issues
may reoccur. You could then point users to include the compatibility
check script and if it flags anything, follow the instructions given.

 - Godmar

On Fri, Jun 6, 2008 at 4:28 AM, Adriano <adrianomassi@...> wrote:
>
> Yes, it would be great if somebody in Michelin would realize that
> their API's are not compatible with one of the most widely used JS
> framework and rush to fix the problem...
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jQuery Development" group.
To post to this group, send email to jquery-dev@...
To unsubscribe from this group, send email to jquery-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---