Unfortunately this caused a regression. Reduced testcase: ``` data:text/html,<select><option></option><option>AAAA</option><option>BBBBBBBBBBBBBBBBBBBBBB</option></select> ``` That ^^ URL should render with a wide, blank select element. But as of this bug, it renders with a skinny select element instead (until you choose a nonempty option, at which point it gets wide). Before this bug's patch landed, we rendered this select element at a consistent wide side (wide enough for the widest option). We don't want to break that behavior. In some cases we'd leave the patch in and track this issue in a followup, but the cost/benefit here leans in favor of just backing out and fixing this issue up-front so that we don't ship with this regression and potentially break site layouts for sites with empty initial-options for select elements.
Bug 1562057 Comment 20 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Unfortunately this caused a regression. Reduced testcase: ``` data:text/html,<select><option></option><option>AAAA</option><option>BBBBBBBBBBBBBBBBBBBBBB</option></select> ``` That ^^ URL should render with a wide, blank select element. But in builds with this bug's patch, it renders with a skinny select element instead (until you choose a nonempty option, at which point it gets wide). Before this bug's patch landed, we rendered this select element at a consistent wide side (wide enough for the widest option). We don't want to break that behavior. In some cases we'd leave the patch in and track this issue in a followup, but the cost/benefit here leans in favor of just backing out and fixing this issue up-front so that we don't ship with this regression and potentially break site layouts for sites with empty initial-options for select elements.