Kurt Hoyt

Worse - it appears that this _patch_ release adds a dependency on @azure/identity 1.3.0, which has a transitive dependency on something called 'keytar', that requires a download and compile of...

@googlebot I signed it!

I wasn't sure whether the check was needed with each call, but that sounds a bit more resilient. I'll give this a try.

Interesting. It doesn't work on any version of IE11 for us. My particular setup is Windows 10 Enterprise (1803), OS build 17134.885, using IE11 11.0.135 (11.885.17134.0). I have the page...

I just tried the URL in my last message on Windows 10 Pro (1903), OS build 18362.267 with IE11 11.0.135 (11.239.13262.0) and it fails as I expect. It only fails...

I disagree - it's quite normal in integration environments, where we may use iframe from different hosts, to set document.domain to the same value (a more general domain) so that...

And my assertion is that its use should **not** cause breakage. Which is borne out by the behavior of every other browser, including Edge. If, in the end, we can't...

First, many thanks to anyone who may be looking at this. Here is more data from moving up the stack: The exception is thrown in the replacement for Node.prototype.appendChild found...

The next level down in my investigation points to the `inertDoc` created in packages/shadydom/src/patches/ElementOrShadowRoot.js. I'm guessing that `document.implementation.createHTMLDocument('inert')` creates a document object that does **not** have the same domain as...

My suspicion was correct. If I add this to ElementOrShadowRoot.js right after `inertDoc` is created: ``` if (inertDoc.domain !== document.domain) { inertDoc.domain = document.domain; } ``` and then setting innerHTML...