3 messages in com.googlegroups.jquery-devRe: Jquery and ViaMichelin Maps Api P...
FromSent OnAttachments
AdrianoJun 4, 2008 1:01 am 
AdrianoJun 5, 2008 1:45 am 
AdrianoJun 6, 2008 1:28 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Jquery and ViaMichelin Maps Api ProblemActions...
From:Adriano (adri@gmail.com)
Date:Jun 5, 2008 1:45:37 am
List:com.googlegroups.jquery-dev

Thank to you all for your kind replies...

unfortunately it looks that the ViaMichelin developer blog isn't working very well... the form for signaling problems doesn't work....

To Jorn: we coud, but whe have to set up a three panes layout so we are looking for a more simple solution, in the worst case we would be trying something similar to what you said... Thanx!

it looks I'll have to switch to another framework, even if EXT also gives a similar error... It's too bad since we where already utilising jQuery for other things...

Ok, again, thank you all

Best regards

On 4 Giu, 17:17, "Jörn Zaefferer" <joer@googlemail.com> wrote:

Could you run the map component in an iframe, to sandbox the JS, while using jQuery for the embedding page?

Jörn

On Wed, Jun 4, 2008 at 5:09 PM, Sam Collett <sam.@gmail.com> wrote:

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 <jere@gmail.com>:

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