element click: descendants of <optgroup disabled> should not be clickable/clearable
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
This is a follow-up from https://github.com/w3c/webdriver/issues/1187 where <option disabled>’s selectedness state is toggled when Element Click is invoked on it.
There is a similar case for descendants of a disabled option grouping:
<select>
<optgroup disabled>
<option>foo
</optgroup>
</select>
In this case the <option> is implictly disabeld because its containing element is disabled. This is unfortunately not refleced in its content IDL disabled attribute, so we must find its closest anscestor to determine if it is.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Element Click behavior described here and compare it with the linked WebDriver issue 1187. Use the provided select/disabled optgroup example to trace how a descendant option is treated. Done means descendants of a disabled optgroup are neither clickable nor clearable, including when the option's disabled IDL attribute does not reflect the inherited state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100