when using non-native DOM implementations.
My initial review of #274 and your change seems to make sense, however....
It looks like you made your change directly to ./chai.js, which is the browser distribution automatically built from the internal source files. Consequently, it means that the CI build was not based on your change. Also, this file is built automatically when you run the test suite locally so it is pretty obvious this is an untested change.
Please make your change to the appropriate source file within ./lib so that it persists. Also, please review our code style guidelines (link). Specifically, your comments exceed the max line width of 80 characters and your tabbing is inconsistent with the rest of the document. Finally, your PR should NOT include ./chai.js; changes to that file are only committed on a version release.
Resource: contribution guide.
Rewrite pretty-printing HTML elements to prevent throwing internal er…
Fixes errors occuring when using a non-native DOM implementation
My apologies, I have now submitted a new commit, which does follow the coding style guidelines.
The fallback for objects which do somehow show up as a false positive for isDomElement are rendered as normal object, meaning their keys are listed.
I do hope this is up to standards.
Any news on merging this pull request?
I was having the same issue with chai blowing up trying to format a non-native XML DOM object. I applied the patch locally and it works for me.