- From: Caridy Patiño <notifications@github.com>
- Date: Mon, 10 May 2021 21:27:38 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 11 May 2021 04:27:51 UTC
From what I remember when we discussed this during the F2F meeting, @mfreed7 mentioned that one possible explanation for the current behavior in chrome could be attributed to the customization of built-ins, in this case, the customization of the `<p>` element. He initial reaction (from what I can remember) was that this could be fixed to have a consistent behavior between the `<p>` and the custom element, which seems to be behaving correctly in all browsers, meaning the `<p>` should be created from the main window. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/977#issuecomment-837781860
Received on Tuesday, 11 May 2021 04:27:51 UTC