disabled: introduce new, recursive definition
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
WebDriver currently references the HTML standard’s definition of disabled. Due to the uniqueness of <select> elements we cannot rely on the content IDL attribute to tell if an <option> is disabled because they inherit the disabledness state from their ancestors.
Consider the following HTML where the <option> element is now disabled:
<select disabled>
<option>foo
</select>
The same idea applies when <optgroup disabled> is used:
<select>
<optgroup disabled>
<option>foo
</optgroup>
</select>
This needs to be resolved before https://github.com/w3c/webdriver/issues/1190.
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 HTML standard’s definition of disabled and compare it with the two examples in this issue. Check issue #1190 for the dependency; this is done when the definition accounts for disabledness inherited through select and optgroup ancestors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100