[whatwg] the impact of <select>.value behavior clearing current selection prior to setting the new selection

Jon Lee jonlee at apple.com
Tue Jan 3 16:04:46 PST 2012


A long while ago[1] there was a clarification[2] made to the html5 spec about how setting selectedIndex and value clears out the selectedness of all options prior to setting the selection. As of this writing, Safari, Chrome, Opera, and Firefox leave the selection alone if the code sets value to null or a string that does not match any of the existing options. I was wondering if anyone had any insight on impact for existing websites with this new behavior.


[1] http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2008-October/016842.html
[2] http://html5.org/tools/web-apps-tracker?from=2292&to=2293

More information about the whatwg mailing list