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

I'm adding my voice to the silent chorus of voices who think it's worth breaking backward compatibility to remove this "wart" from the web platform. And I'm adding it now because I've been working with the DOM for over a decade and I've HATED it ... until recently.

Programming against the DOM today is a vastly superior experience than its ever been and I'm grateful that some of you decided that the ease of use consideration of an API matters and have thus made significant improvements to it.  And then a couple days ago I write some code with the reasonable expectation that the selected option would be retained in the clone. That expectation was violated when today I got a bug report from the testing group. Now remember, I know the DOM and I know that this happens, but I forgot, because I'm human and in recent years the DOM has been reasonable, and the expectation is also reasonable. So if someone with my experience forgets, consider new web developers who are just learning the DOM.

I'm not of the opinion that breaking backwards compatibility for this specific issue is an apocalyptic event so I hope those who have the power to "fix" it  will. But I could be wrong so I'm going to go out and stock up on canned goods just in case :smile_cat: 

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