Other than using a timer to count the number of elements over time and looking for changes, I can't think of a better way to simulate this event.
Is there some sort of proprietary IE version of DOMNodeInserted? Thanks.
Other than using a timer to count the number of elements over time and looking for changes, I can't think of a better way to simulate this event.
Is there some sort of proprietary IE version of DOMNodeInserted? Thanks.
No, there isn't. The nearest is the propertychange
event, which fires in response to a change in an attribute or CSS property of an element. It fires in response to changing the innerHTML
property of an element directly but not when the contents of the elements are altered by some other means (e.g. by using DOM methods such as appendChild()
or by altering the innerHTML
of a child element).
As pointed out in the comments, there is a workaround. It's based on an elaborate hack and I'd recommend using mutation observers instead wherever possible. See @naugtur's answer for details. @naugtur's answer has been deleted but the solution can be found at https://github.com/naugtur/insertionQuery
propertychange
does not fire for innerHTML
when the content of an element changes by any means other than setting its innerHTML
property directly, which makes it pretty much useless as a workaround for DOMNodeInserted
: jsfiddle.net/eze5V/8. I've updated my answer. –
Amado You can over-ride all the DOM-manipulation methods - appendChild, insertBefore, replaceChild, insertAdjacentHTML, etc - and monitor innerHTML with onpropertychange.
You might be able to come up with a solution that satisfies your requirements.
BTW, it seems that DOMNodeInserted, etc will be deprecated by browsers in the future. See http://www.w3.org/TR/DOM-Level-3-Events/#events-mutationevents
onreadystatechange will work in IE. A DHTML behavior must be attached to the element via htc, but the htc file does not have to exist:
if (!!document.addEventListener)
{
$(domnode).get(0).addEventListener("DOMNodeInserted", fixtext, false);
}
else
{
$(domnode).get(0).addBehavior("foo.htc");
$(domnode).get(0).attachEvent("onreadystatechange", fixtext);
}
A dirty workaround is to intercept the prototype methods of type Element as follows:
window.attachEvent('onload', function() {
invokeNodeInserted(document);
(function(replace) {
Element.prototype.appendChild = function(newElement, element) {
invokeNodeInserted(newElement);
return replace.apply(this, [newElement, element]);
};
})(Element.prototype.appendChild);
(function(replace) {
Element.prototype.insertBefore = function(newElement, element) {
invokeNodeInserted(newElement);
return replace.apply(this, [newElement, element]);
};
})(Element.prototype.insertBefore);
(function(replace) {
Element.prototype.replaceChild = function(newElement, element) {
invokeNodeInserted(newElement);
return replace.apply(this, [newElement, element]);
};
})(Element.prototype.replaceChild);
});
Using onreadystatechange as suggested by Paul Sweatte does not really work. The readystatechange event is only triggered while loading foo.htc. It has nothing to do with changing the DOM node.
I've set up a little fiddle to demonstrate it. Have a look at http://jsfiddle.net/Kermit_the_frog/FGTDv/ or http://jsfiddle.net/Kermit_the_frog/FGTDv/embedded/result/.
HTML:
<input type="button" id="fooBtn" value="add" />
<div id="fooDiv"></div>
JS/Jquery:
function bar(e) {
var state = $('#fooDiv').get(0).readyState;
alert (state);
}
$("#fooBtn").on("click", function(){
$('#fooDiv').get(0).addBehavior("foo.htc");
$('#fooDiv').get(0).attachEvent("onreadystatechange", bar);
});
As you can see: even though there is no DOM manipulation going on there is a readystatechange event.
Seems, DHTML Behaviors can be used in IE to emulative DOMNodeInserted
.
© 2022 - 2024 — McMap. All rights reserved.