Re: [whatwg/dom] Define cloning steps for an select element (#644)

If someone creates a library which clones select state too, and it becomes of a similar level of popularity as cloneNode, that would be a great signal that we should reconsider this. At this point we are weighing three web developers who want to write less code, against the cost of propogating a legacy mistake throughout more of the platform.

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.) And you're right that if we were to find out that this was a widespread need, we'd want to do it via a different function, which wasn't focused around cloning the tree structure like cloneNode is, and instead is focused around cloning the state. But we simply do not have evidence that enough developers are running into this, to make it important to add a sugar function to the web platform, to save them writing some code. And no amount of GitHub comments will really get us there; the best path is to show wide adoption of a library.

So hopefully the next steps here are clearer now!

-- 
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-442840157