René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Created \"null\" option into select ng-options sets to false when other option is clicked","articleBody":"**I'm submitting a ...**\r\n- [ ] regression from 1.7.0\r\n- [ ] security issue\r\n- [ ] issue caused by a new browser version\r\n- [x] other \u003c!--(Please do not submit support requests here - see above)--\u003e\r\n\r\n**Current behavior:**\r\nEntering a page which has an hardcoded option with null value gets the parameter `selected=\"false\"` and creating problems on Chrome when new data is put on the object supplied in ng-options.\r\n\r\n**Expected / new behavior:**\r\nThe parameter `selected=\"false\"` could be dropped when not selected. When selected, could just be `selected`\r\nThis was fixed in [https://github.com/angular/angular.js/commit/27486bd15e70946ece2ba713e4e8654b7f9bddad](url) but looks like is not used on select options.\r\n\r\n**Minimal reproduction of the problem with instructions:**\r\nOn this example [plunkr](https://plnkr.co/edit/2H6bbXDP2iWt7rz3GhcF?p=preview), the default option can be left as is, then by clicking on the button \"add\", on Chrome only, the select box will change to the option called \"none\". On Firefox, only page source is changed.\r\n\r\n**AngularJS version:**\r\n1.7.8\r\n\r\n**Browser:** \r\nChrome 78.0.3904.97 (64 bit) (select button displays wrong data)\r\nFirefox 68.2.0esr (64-bit) (only visible on page source, rendered select box keeps the same)\r\n(both running in Debian 9)\r\n\r\n**Anything else:**\r\nUsing jquery 2.2.4\r\nCould be related with [https://github.com/angular/angular.js/issues/16916](url) due to ambiguity of the selected option which should be displayed.\r\n","author":{"url":"https://github.com/mjmlopes","@type":"Person","name":"mjmlopes"},"datePublished":"2019-11-18T18:11:15.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/16917/angular.js/issues/16917"}