- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Tue, 24 Feb 2015 09:14:40 +0100
- To: Ryosuke Niwa <rniwa@apple.com>
- Cc: Boris Zbarsky <bzbarsky@mit.edu>, WebApps WG <public-webapps@w3.org>, Yehuda Katz <wycats@gmail.com>
On Mon, Feb 23, 2015 at 11:58 PM, Ryosuke Niwa <rniwa@apple.com> wrote: > In that regard, perhaps what we need another option (although 4 might be a developer friendly superset of this): > 5) Don't do anything. Custom elements will be broken upon cloning if there are internal states other than attributes just like cloning a canvas element will lose its context. Putting state in a known place as with 3 also seems okay. Although if anything throws there you would have to catch and ignore it. But yes, perhaps 5 is a good start as that is what custom elements provide for today... -- https://annevankesteren.nl/
Received on Tuesday, 24 February 2015 08:15:10 UTC