Related to this:

http://groups.google.com/group/prototype-core/browse_thread/thread/2667e1d75a647ec5
( Conflict 1.6 with Virtual Earth in FireFox)

Atlascompat.js also prototypes some methods on the native Element
definition.

In this case it can be solve by first loading the atlas stuff and then
then prototype.js

On Feb 18, 5:36 pm, Sjoerd Mulder <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> Why is prototype framework overwriting the (native) Element object /
> constructor and setting it's own function?
>
> This breaks a lot of functionality in other frameworks which are
> prototyping some Methods on the (native) Element, for example:
> "selectNodes" / "selectSingleNode" to emulate IE XPath in other
> browsers (Fx, Op, Sf), See (http://dev.abiss.gr/sarissa/)
>
> I have tried to access the original constructor even on different way
> like:
>
> "new DOMParser().parseFromString('<test />', 'text/
> xml').documentElement.constructor" but that also returns the
> prototype.js function.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Prototype: Core" group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to