A form control in a disabled FIELDSET in the LEGEND of another disabled FIELDSET should be disabled |
||
Issue descriptionChrome Version: 66 canary OS: All but iOS What steps will reproduce the problem? (1) Open the following HTML document: <fieldset disabled> <legend> <fieldset disabled> INPUT in disabled fieldset in the legend of the disabled fieldset. <input> </fieldset> </legend> </fieldset> What is the expected result? The INPUT field should be disabled. Clicking on it doesn't set focus on it. What happens instead? The INPUT field is enabled. Clicking on it sets focus on it. Please use labels and text to provide additional information. Safari: OK Firefox: OK
,
Feb 28 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/1e8cf988bac408513d01e37a10b8cc1d55f567ad commit 1e8cf988bac408513d01e37a10b8cc1d55f567ad Author: Kent Tamura <tkent@chromium.org> Date: Wed Feb 28 10:12:56 2018 Fix a bug of <fieldset disabled> detection logic. HTMLFormControlElement::UpdateAncestorDisabledState() checked if the highest <legend> is the first <legend> child of the highest disabled <fieldset>. It should check <lengend> child of every disabled fieldset ancestors. Bug: 817181 Change-Id: I8f7dedd8089757d9eae726de359b0efe47cf9f44 Reviewed-on: https://chromium-review.googlesource.com/940644 Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#539776} [modify] https://crrev.com/1e8cf988bac408513d01e37a10b8cc1d55f567ad/third_party/WebKit/LayoutTests/external/wpt/html/semantics/forms/the-fieldset-element/disabled-001.html [modify] https://crrev.com/1e8cf988bac408513d01e37a10b8cc1d55f567ad/third_party/WebKit/Source/core/html/forms/HTMLFormControlElement.cpp
,
Feb 28 2018
|
||
►
Sign in to add a comment |
||
Comment 1 by tkent@chromium.org
, Feb 28 2018Status: Started (was: Available)