Most recent version 4.2.14 breaks IE11

[yc-yvonne]

Likely from this: #668

Causes a Internet Explorer throws SCRIPT5022: HierarchyRequestError in IE11

Method of injection is not supported

[tiagomsg]

Have the same issue, it's definitely due to #668.

parentNode.constructor.name returns undefined on IE11, that causes this switch to assume the domRoot is the parentNode instead of parentNode.head.

Think the fix would be to just change that switch to:

    switch (parentNode.constructor.name) {
      case 'ShadowRoot':
        domRoot = parentNode;
        break;
      case 'HTMLDocument':
      default:
        domRoot = parentNode.head;
        break;
    }

But not entirely sure if this is safe or if it'll break something else.

[kraMaddi]

Getting the same issue for safari as well.
hierarchyrequesterror: the operation would yield an incorrect node tree.
The older version works fine

[geoffharcourt]

We're seeing this issue in all of our Jest tests that use components with react-tooltip. I'm not sure yet if it's Jest itself or jsdom, but we this is the trace we see:

console.error
--
  | Error: Uncaught [HierarchyRequestError: Invalid insertion of STYLE node in #document node.]
  | at reportException (/app/node_modules/jsdom/lib/jsdom/living/helpers/runtime-script-errors.js:62:24)
  | at innerInvokeEventListeners (/app/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:333:9)
  | at invokeEventListeners (/app/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:274:3)
  | at HTMLUnknownElementImpl._dispatch (/app/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:221:9)
  | at HTMLUnknownElementImpl.dispatchEvent (/app/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:94:17)
  | at HTMLUnknownElement.dispatchEvent (/app/node_modules/jsdom/lib/jsdom/living/generated/EventTarget.js:231:34)
  | at Object.invokeGuardedCallbackDev (/app/node_modules/react-dom/cjs/react-dom.development.js:237:16)
  | at invokeGuardedCallback (/app/node_modules/react-dom/cjs/react-dom.development.js:292:31)
  | at commitRootImpl (/app/node_modules/react-dom/cjs/react-dom.development.js:22541:9)
  | at unstable_runWithPriority (/app/node_modules/scheduler/cjs/scheduler.development.js:653:12) DOMException {}
  |  
  | at VirtualConsole.<anonymous> (node_modules/jsdom/lib/jsdom/virtual-console.js:29:45)
  | at reportException (node_modules/jsdom/lib/jsdom/living/helpers/runtime-script-errors.js:66:28)
  | at innerInvokeEventListeners (node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:333:9)
  | at invokeEventListeners (node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:274:3)
  | at HTMLUnknownElementImpl._dispatch (node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:221:9)
  | at HTMLUnknownElementImpl.dispatchEvent (node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:94:17)

[KumarSumitD]

We are also getting the same error on IE11. Is reverting to 4.2.13 fixes the issue ?

[rossettistone]

@KumarSumitD Reverting to 4.2.13 resolved the issue for us.

[handofthecode]

HierarchyRequestError: The operation would yield an incorrect node tree.
Safari: 14.0.3
react-tooltip: 4.2.17

[dworzycp]

Same issue here in 4.2.17

[ruMoonGuard]

Same issue here in 4.2.19

[rscotten]

Confirmed that reverting back to 4.2.13 resolves the issue.