On Mon, Feb 23, 2015 at 11:58 PM, Ryosuke Niwa <rn...@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/
