- From: Vladimir Varlamov <notifications@github.com>
- Date: Mon, 03 Dec 2018 02:59:43 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 3 December 2018 11:00:04 UTC
>> A tree-cloning function that also copies a few small pieces of state if the nodes of the tree have certain names is not good design. (That's the legacy mistake I refer to.) > This is soooooo true! No form elements should have ever cloned state IMO. Could you describe in more detail why or give examples of usage without cloning state? > Perhaps there should be a clean clone operation that doesn't copy state, ever What is the meaning to separate state and tree? Why the state is considered in this case separately but not just as a set of object properties (correct if I misused the definition. I mean the opposite of element attributes)? -- 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/issues/644#issuecomment-443670631
Received on Monday, 3 December 2018 11:00:04 UTC