Problem with 1.46 displayCredits() in Firefox and Edge when switching imagery

CesiumJS
1

I’m having a problem with Cesium 1.46, Firefox, Edge (but not Chrome) - I get the following stacktrace when switching to another imagery provider.

This doesn’t make any sense, but in the function displayCredits() the reference to childNodes ie

var childNodes = container.childNodes;

seems to fail in FF & Edge when the remaining nodes are removed at the bottom of the method (childNode.length does not change after removeChild() is called):

    while (domIndex < childNodes.length) {
        container.removeChild(childNodes[domIndex]);
    }

If I replace the reference ‘childNodes’ with ‘container.childNodes’ (ie. not using the reference) then the problem goes away.
I can’t reproduce this in sandcastle.

An error occurred while rendering. Rendering has stopped.
undefined
Error: NotFoundError
removeChild@http://localhost:8080/ActiveFlightDemoModule/activeflight/bower_components/webcomponentsjs/webcomponents.js:1878:19
displayCredits@http://localhost:8080/ActiveFlightDemoModule/activeflight/Cesium/Cesium.js:204229:13
CreditDisplay.prototype.endFrame@http://localhost:8080/ActiveFlightDemoModule/activeflight/Cesium/Cesium.js:204554:9
render@http://localhost:8080/ActiveFlightDemoModule/activeflight/Cesium/Cesium.js:232612:9
tryAndCatchError@http://localhost:8080/ActiveFlightDemoModule/activeflight/Cesium/Cesium.js:232618:13
Scene.prototype.render@http://localhost:8080/ActiveFlightDemoModule/activeflight/Cesium/Cesium.js:232662:13
CesiumWidget.prototype.render@http://localhost:8080/ActiveFlightDemoModule/activeflight/Cesium/Cesium.js:242724:13
render@http://localhost:8080/ActiveFlightDemoModule/activeflight/Cesium/Cesium.js:242105:25

Thanks for your help,
Peter

2

Looking closely at your callstack, the error is actually coming from a file in your application called webcomponents.js. Searching around I found that this appears to be a library which is replacing the browser’s built-in removeChild method with its own implementation, which presumably has a bug.

You might try contacting that library with a reproducible example and see if they can fix their code.