Skip to content

The defaultValue of <select> may be broken #11099

@StoneCypher

Description

@StoneCypher

I would like to report a bug.

In re-filing another outstanding bug that was closed despite being reproducible, I decided to create a repro case.

Since the repro involves setting defaultValue on a <select>, I confronted the human inability to remember whether HTML is zero-indexed or one-indexed.

Since the repro also involves determining whether a given <option> is selectable, I decided to just have a control with four <option>s and to select 3, to see which I'd get - the third or the fourth.

Joke's on me. I got neither. I got the first selectable <option>.

A winner is testcase. If the series is 1-indexed you should see joe; if 0-indexed you should see stan. Instead you see bob.

As such I currently believe that defaultValue is not honored on select.

This is the first time I've noticed this. I have only tested it under 16.0.0.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions