On May 6, 2015, at 9:48 PM, Anne van Kesteren ann...@annevk.nl wrote:
On Thu, May 7, 2015 at 12:23 AM, Ryosuke Niwa rn...@apple.com wrote:
Are you suggesting that cloning my-button will create a new instance of
my-button by invoking its constructor?
No, I'm saying there would be another
Open issues are kept track of here:
https://wiki.whatwg.org/wiki/Custom_Elements
I think the most pragmatic way forward here is accepting that
constructing and upgrading need not be tied.
Synchronous constructors map most closely to what browsers do today
for builtin elements and open up the
On May 6, 2015, at 8:37 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Wed, May 6, 2015 at 4:59 PM, Dimitri Glazkov dglaz...@google.com wrote:
On Wed, May 6, 2015 at 7:50 AM, Domenic Denicola d...@domenic.me wrote:
Can you explain how you envision cloning to work a bit more? Somehow there
On Wed, May 6, 2015 at 4:59 PM, Dimitri Glazkov dglaz...@google.com wrote:
On Wed, May 6, 2015 at 7:50 AM, Domenic Denicola d...@domenic.me wrote:
Can you explain how you envision cloning to work a bit more? Somehow there
will be instances of these elements which are not created by their
On Wed, May 6, 2015 at 7:50 AM, Domenic Denicola d...@domenic.me wrote:
Can you explain how you envision cloning to work a bit more? Somehow there
will be instances of these elements which are not created by their
constructors?
Also, how is it in any way similar to how canvas or input work?
On Thu, May 7, 2015 at 12:23 AM, Ryosuke Niwa rn...@apple.com wrote:
Are you suggesting that cloning my-button will create a new instance of
my-button by invoking its constructor?
No, I'm saying there would be another primitive operation, similar to
the extended structured cloning proposed
