- From: Dmitry IV. <notifications@github.com>
- Date: Tue, 27 Oct 2020 19:23:04 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 28 October 2020 02:23:16 UTC
Sorry for possibly duplicating issue, please redirect to existing discussion (parsedCallback or etc.). Just wanted to point out to obscure API aspect. ```html <script> customElements.define('x-x', class extends HTMLElement { connectedCallback() { console.log(this.innerHTML) } }) </script> <x-x>123</x-x> ``` The element is rendered in DOM as `123`, but `innerHTML`/`textContent` is empty. Is that rendered/API state mismatch correct? Expectation: it should either return `innerHTML` with factually rendered content, or if `innerHTML` is empty then it should not render `123`. Current behavior blocks some practical solutions. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/903
Received on Wednesday, 28 October 2020 02:23:16 UTC