Thanks John.
My point is that dom:loaded should ensure a successful appendChild on
document.body in all cases, not throwing the random IE Operating
Aborted. Using the scroll approach ensures this, it's more accurate
then the current implementation and will prevent having to use those
For that you would probably need to extend or modify Ajax.Response
class (i.e. its constructor which initializes responseXML property)
- kangax
On May 12, 10:19 am, disccomp [EMAIL PROTECTED] wrote:
Is it possible to extend xmlResponse with Object.methods like select?
Nick,
happy to see the doScroll fit your needs too.
I also noticed in your previous message you said:
Inserting to the top works however, so insert before firstChild works,
You did realize too that this is the most clean way when applicable,
adding widget to a page shouldn't require the use of
Tobie / Samuel,
this is the second test case I promised about the DOMContentLoaded
patch that Samuel kindly assembled. Since it is bigger than the
previous
test I prefer to temporarily publish the tests on my site:
http://javascript.nwbox.com/IEContentLoaded/prototype/tester.html
IE has issues extending XML Nodes.
See http://dev.rubyonrails.org/ticket/9709
You must use Element#methodName instead or make a wrapper for it:
Something like:
(function( ) {
var methods = Object.keys(Element.Methods).inject({ }, function(m,
name) {
m[name] = function() {
return
Diego Perini,
in IE dom:loaded is a custom event, custom event use the
ondataaviable event as a vessel to ride the event bubble and other
things.
that is why you see that. use event.eventName instead of
event.eventType.
- JDD
--~--~-~--~~~---~--~~
You received
Added the following updates to the event system in my fork:
Fix issue with how IE wrappers.dispatcheriterates over list of
wrappers:
http://github.com/jdalton/prototype/commit/bfa0ea8da441d53983dd4223248991b3329ab93f
Add unit tests for the wrapers.dispatcher fix :
I just looked through the code and realized we were handling the
IFrame issue :), thanks Diego for pointing that out :).
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Prototype: Core group.
To post to this group,
