Related issue: https://bugs.chromium.org/p/chromium/issues/detail?id=249515 Test case: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/4892 HTML standard: [[ The following content attributes must not be specified and do not apply to the element: ... readonly, ... ]] https://html.spec.whatwg.org/#range-state-(type=range) In Gecko and Edge, readonly does not apply as per spec. WebKit is like Chromium (will report). I think the WebKit/Chromium is confusing UI. (Credit to chaals for bringing this to my attention in https://github.com/whatwg/html/issues/2311#issuecomment-278002216 )
RangeInputType::handle*Event() mistakenly use isDisabledOrReadOnly() instead of isDisabledFormControl().
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/9c948b9d9ed4d886e54f22a4a6705c9470213c09 commit 9c948b9d9ed4d886e54f22a4a6705c9470213c09 Author: ratsunny <ratsunny@gmail.com> Date: Mon Feb 20 01:29:25 2017 Ignore the |readonly| attribute in <input type=range> Attribute |readonly| must be ignored in <input type=range> per spec [1] Test was changed accordingly [1] https://html.spec.whatwg.org/#range-state-(type=range) BUG= 693037 Review-Url: https://codereview.chromium.org/2703013002 Cr-Commit-Position: refs/heads/master@{#451539} [modify] https://crrev.com/9c948b9d9ed4d886e54f22a4a6705c9470213c09/third_party/WebKit/LayoutTests/fast/forms/range/range-drag-expected.txt [modify] https://crrev.com/9c948b9d9ed4d886e54f22a4a6705c9470213c09/third_party/WebKit/LayoutTests/fast/forms/range/range-drag.html [modify] https://crrev.com/9c948b9d9ed4d886e54f22a4a6705c9470213c09/third_party/WebKit/Source/core/html/forms/RangeInputType.cpp [modify] https://crrev.com/9c948b9d9ed4d886e54f22a4a6705c9470213c09/third_party/WebKit/Source/core/html/shadow/SliderThumbElement.cpp
Comment 1 by tkent@chromium.org
, Feb 17 2017Status: Available (was: Untriaged)