Failed to execute ‘removeChild’ on ‘Node’

Posted on

Failed to execute ‘removeChild’ on ‘Node’ – Even if we have a good project plan and a logical concept, we will spend the majority of our time correcting errors abaout javascript and javascript. Furthermore, our application can run without obvious errors with JavaScript, we must use various ways to ensure that everything is operating properly. In general, there are two types of errors that you’ll encounter while doing something wrong in code: Syntax Errors and Logic Errors. To make bug fixing easier, every JavaScript error is captured with a full stack trace and the specific line of source code marked. To assist you in resolving the JavaScript error, look at the discuss below to fix problem about Failed to execute ‘removeChild’ on ‘Node’.

Problem :

I’m using http://alexgorbatchev.com/SyntaxHighlighter/ to highlight code on my website but sometimes in my log im getting Javascript errors like this :

Uncaught NotFoundError: Failed to execute ‘removeChild’ on ‘Node’: The node to be removed is no longer a child of this node. Perhaps it was moved in a ‘blur’ event handler?

Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.

// set up handler for lost focus
attachEvent(textarea, 'blur', function(e)
{
   textarea.parentNode.removeChild(textarea);
   removeClass(highlighterDiv, 'source');
});

Here is the attachEvent() function code :

function attachEvent(obj, type, func, scope)
{
    function handler(e)
    {
        e = e || window.event;
        
        if (!e.target)
        {
            e.target = e.srcElement;
            e.preventDefault = function()
            {
                this.returnValue = false;
            };
        }
            
        func.call(scope || window, e);
    };
    
    if (obj.attachEvent) 
    {
        obj.attachEvent('on' + type, handler);
    }
    else 
    {
        obj.addEventListener(type, handler, false);
    }
};

Can anyone help getting this fixed ?

Solution :

I had to deal with the same issue, and the answer is confusing and counter intuitive. Well, it has its logic, but leads to non-trivial behaviours.

Essentially, when a node is removed from the DOM tree, it fires a blur event (and before a focusout event too).

So, when you call removeChild, the blur event is fired again, but this time textarea still has its parentNode defined, but textarea isn’t among its parent’s children anymore! (Yes, read this twice. Or more.)

This happens in Chrome for now, although Firefox has planned to do the same for quite some time.

As a workaround, you can remove the event listener you attached:

var onblur = function(e) {
    detachEvent(textarea, 'blur', onblur);
    textarea.parentNode.removeChild(textarea);
    removeClass(highlighterDiv, 'source');
};
attachEvent(textarea, 'blur', onblur);

I’m assuming that you have some detachEvent function to remove event listeners. Adjust the code to your needs.

Alternatively, you can set a flag (like a property, or an attribute, or better a scoped variable) on the textarea in the listener function, and check for it before proceeding with the node removal:

var removed = false;
attachEvent(textarea, 'blur', function(e) {
    if (removed) return;
    removed = true;
    textarea.parentNode.removeChild(textarea);
    removeClass(highlighterDiv, 'source');
});

You can also check if textarea if actually a child node of its parentNode before removing it, but such test is so counter-intuitive (at least to me) that I wouldn’t recommend doing that, in fear that this behaviour will be changed in the future.

Finally, you can always rely on a try...catch statement, but… ugh.

2016 Update

Naturally, using a framework like jQuery would save you a lot of work attaching event listeners with one, but this functionality will come to standard addEventListener too:

textarea.addEventListener('blur', handler, { once: true });

While the classic answer for this question was that it’s a bug in the JS code, with React 16 there is a major bug which means that any browser/extension mechanism which modifies the DOM breaks React.

Google Chrome’s built in Translate functionality is the most common culprit.

GitHub issue: https://github.com/facebook/react/issues/11538

Minimal case: https://p93xxmr0rq.codesandbox.io/ (just manually right click “Translate to” in Chrome and select from Japanese then click the button)

Workaround: How to disable google translate from html in chrome

<meta name="google" content="notranslate">

I’m going out on a limb here and assuming that some of you who find this question are here because you googled the error quoted above:

‘removeChild’ on ‘Node’: The node to be removed is no longer a child
of this node. Perhaps it was moved in a ‘blur’ event handler?

I’m using jQuery & DataTables 1.10.6 and this error was indeed coming up on a blur() event where I was updating the cell value. The solution for me was to add a condition inside the event like this:

var blur = false;
$('table').on('blur', 'td select', function() {
    if (!blur) {
        blur = true;
        var cell = $(this).closest('td');
        table.cell(cell).data('example data');
        blur = false;
    }
});

I would be very surprised if there weren’t a much better solution but hopefully this helps someone and maybe garners some constructive comments.

Try to translate your site with Google Chrome (right click on the site and choose “Translate to English”. If you see the error happening in the console, then you know it’s caused by Google Translate.

Related GitHub issue: https://github.com/facebook/react/issues/11538.


Workaround from Dan Abramov:

if (typeof Node === 'function' && Node.prototype) {
  const originalRemoveChild = Node.prototype.removeChild;
  Node.prototype.removeChild = function(child) {
    if (child.parentNode !== this) {
      if (console) {
        console.error('Cannot remove a child from a different parent', child, this);
      }
      return child;
    }
    return originalRemoveChild.apply(this, arguments);
  }

  const originalInsertBefore = Node.prototype.insertBefore;
  Node.prototype.insertBefore = function(newNode, referenceNode) {
    if (referenceNode && referenceNode.parentNode !== this) {
      if (console) {
        console.error('Cannot insert before a reference node from a different parent', referenceNode, this);
      }
      return newNode;
    }
    return originalInsertBefore.apply(this, arguments);
  }
}

Run this code before your app is rendered. Please keep in mind, that this has a slight performance hit.


Workaround from Shuhei Kagawa

Render texts in <span>.

// Case 1
<div>
  {condition && 'Welcome'}
  <span>Something</span>
</div>

// A workaround for case 1
<div>
  {condition && <span>Welcome</span>}
  <span>Something</span>
</div>

// Case 2
<div>
  {condition && <span>Something</span>}
  Welcome
</div>

// A workaround for case 2
<div>
  {condition && <span>Something</span>}
  <span>Welcome</span>
</div>

A detailed explanation can be found here:
https://github.com/facebook/react/issues/11538#issuecomment-390386520

I use Time delay and it work for me like this.

    // set up handler for lost focus
    attachEvent(textarea, 'blur', function(e)
    {
        setTimeout(function() {
            textarea.parentNode.removeChild(textarea);
            removeClass(highlighterDiv, 'source');
        }, 0);
    });

Instead of textarea.parentNode.removeChild(textarea); You could use textarea.parentNode.innerHTML = '' or something similar, depending on your context.

I was getting this error and nothing from above helped me, eventually I ended up with just simple :

if (img.parentNode) {
    body.removeChild(img);
}

which works perfectly for me.

I found the same error message on a simple jQuery script.
When I tried to get the height of an element $(‘#element’).height() I saw the same error on the console.

The element exists and $(‘#element’).length was 1.

The log of the element with console.log( $(‘#element’) ) was like a jQuery object but with a lot of methods repeated.

After a lot of debugg I found that adding a $(document).on(‘DOMContentLoaded DOMNodeInserted’) event handler made this weird thing to jQuery objects.

Hope this help someone cause It’s hard to find.

The event types may be different when it’s fired from the program verses from the default action of the Dom. If you check the types, and use an if (type === ‘typeYouWant’) as a guard clause, you can potentially skip the unwanted execution of your code. Console log the event to check if there’s a ‘type’ you can isolate.

   formEditEl.addEventListener('blur', this._cancelEdit.bind(this));

  _cancelEdit(e) {
    if (e.type === "change") document.querySelector('.form__edit').remove();
    };

you need to check each time the method is executed whether the element is a child of the given parent.

if(box.parentElement === parentBox) {
    parentBox.removeChild(box);
}

$("#element_id").remove();

Leave a Reply

Your email address will not be published. Required fields are marked *