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>.

This means you get an `attributeChangedCallback` for `is`, right? And queued mutation observers if you had set those up on yourself. That's what we want?

---
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#r58834645

Received on Thursday, 7 April 2016 08:16:57 UTC