W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2015

RE: Minimum viable custom elements

From: Domenic Denicola <d@domenic.me>
Date: Wed, 14 Jan 2015 18:41:19 +0000
To: Ryosuke Niwa <rniwa@apple.com>
CC: Anne van Kesteren <annevk@annevk.nl>, Erik Arvidsson <arv@google.com>, Boris Zbarsky <bzbarsky@mit.edu>, public-webapps <public-webapps@w3.org>
Message-ID: <CY1PR0501MB13693206A7FE9D180CF8E279DF410@CY1PR0501MB1369.namprd05.prod.outlook.com>
From: Ryosuke Niwa [mailto:rniwa@apple.com] 

> See Boris' responses in another thread [1] and [2].  Jonas outlined how this could work in the same thread [3]

Thanks for the references. But avoiding this problem is exactly what Arv and I were talking about.

The mechanism that createdCallback (and all other custom element callbacks) operate via is to batch up all user code after the parser, but before returning control to script. So in the example of setting innerHTML then reading it on the next line, you let the parser run, *then* run the constructors, then run the next line.

Again, I might be missing something, but if you just do s/createdCallback/constructor in the existing spec, I think you get what we're describing.
Received on Wednesday, 14 January 2015 18:41:49 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:25 UTC