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

Not a single popular site for developer (for example https://developer.mozilla.org/en-US/docs/Web/API/Node/cloneNode) says about this features ("a lot of internal state that is not copied over by cloneNode()"). Now the threshold of entry into the development is very low and most do not even face this error. Because is not hello world difficult. Or they use a library where someone was not too lazy to write a little more code, unless of course he had tested his code enough to find out about this issue.

> becomes of a similar level of popularity as cloneNode

How do you collect statistics? Or should someone open "cloneNodeReallyAll" fan club? 

> At this point we are weighing three web developers who want to write less code

In no case. I just want everything to meet the expected behavior or be documented if it is not. Do you have anything against it?

> the best path is to show wide adoption of a library

What I have to prove that fixed polyfill of cloneNone if gained popularity?
Not everything in IT world should work according to such plan. There are rarely used features and capabilities that someone should take care of and do this dirty work. 

**BUT** in the same time
![doc](http://internal.by/i/20181129175717.png
)

WTF? I do not know this story, but then obviously someone does not bother about backward compatibility at all and your excuses about cloneNode() seem like bullshit!


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