Closed
Bug 577306
Opened 14 years ago
Closed 9 years ago
For disabling options, should only look at the parent optgroup
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
INVALID
People
(Reporter: Ms2ger, Unassigned)
References
()
Details
(Keywords: html5)
Attachments
(2 files, 1 obsolete file)
3.96 KB,
patch
|
smaug
:
review-
|
Details | Diff | Splinter Review |
620 bytes,
text/html
|
Details |
In the testcase at <http://software.hixie.ch/utilities/js/live-dom-viewer/saved/538>, both options should be enabled, as the disabled optgroup is its parent, but rather a grandparent. See <http://www.whatwg.org/html/#concept-option-disabled>.
Reporter | ||
Comment 1•14 years ago
|
||
Still need to find a way to test this.
Reporter | ||
Comment 2•14 years ago
|
||
Attachment #456294 -
Attachment is obsolete: true
Attachment #456431 -
Flags: review?(Olli.Pettay)
Comment 3•14 years ago
|
||
So do you know why html5 defines that behavior.
IMO, it makes more sense to disable everything under a disabled optgroup.
And the patch doesn't seem to work too well with this testcase.
The second option isn't gray'ed out, but user can't select it anyway.
Updated•14 years ago
|
Attachment #456431 -
Flags: review?(Olli.Pettay) → review-
Comment 4•13 years ago
|
||
We could use the patch in bug 759666 and directly use HasState() on the option element?
Comment 5•9 years ago
|
||
I think this is INVALID, because the spec says <option>s that aren't children of the <select> or of <optgroup> children of the <select> are not part of the list of options to start with (bug 1214164).
Flags: needinfo?(Ms2ger)
Reporter | ||
Comment 6•9 years ago
|
||
I'm not working on this bug.
Assignee: Ms2ger → nobody
Status: ASSIGNED → NEW
Flags: needinfo?(Ms2ger)
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•