Re: [whatwg/dom] Upstream Custom Elements (#204)

>  
> - <li>Return a new <a for="/">element</a> that implements <var>interface</var>,
> - with no attributes,
> - <a for=Element>namespace</a> set to the <a>HTML namespace</a>,
> - <a for=Element>local name</a> set to <var>localName</var>, and
> - <a>node document</a> set to the <a>context object</a>.
> + <li>Let <var>element</var> be the result of <a>creating an element</a> given the
> + <a>context object</a>, <var>localName</var>, null, the <a>HTML namespace</a>, <var>is</var>, and
> + with the <var>synchronous custom elements</var> flag set. Rethrow any exceptions.
> +
> + <li>If <var>is</var> is non-null, then <a>set an attribute value</a> for <var>element</var> using
> + "<code>is</code>" and <var>is</var>.

Yeah, I am pretty sure it is. Originally I treated is="" very specially and tried to exclude it from attributeChangedCallback, mutation observers, etc. but it was a big pain for no real gain. This model is much simpler. See https://github.com/w3c/webcomponents/commit/5c4cc14e5f973d81ef9ab672b12951fef2d90471 commit message.

---
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/pull/204/files/58e7dacf2e27ef01b1a353bd081d68a50d5f0e84#r58902938