Bug 168422 - <input type=range readonly> doesn't act per spec
Summary: <input type=range readonly> doesn't act per spec
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Forms (show other bugs)
Version: Safari Technology Preview
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Chris Dumez
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2017-02-16 04:56 PST by Simon Pieters (:zcorpan)
Modified: 2017-02-18 23:24 PST (History)
8 users (show)

See Also:

Attachments
Patch (12.32 KB, patch)
2017-02-18 21:41 PST, Chris Dumez 		no flags Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Pieters (:zcorpan) 2017-02-16 04:56:28 PST 
Related issue: https://bugs.webkit.org/show_bug.cgi?id=168421

(This issue for chromium: https://bugs.chromium.org/p/chromium/issues/detail?id=693037 )

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.

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 )
Comment 1 Radar WebKit Bug Importer 2017-02-18 15:13:02 PST 
<rdar://problem/30593189>
Comment 2 Chris Dumez 2017-02-18 21:41:06 PST 
Created attachment 302067 [details]
Patch
Comment 3 WebKit Commit Bot 2017-02-18 23:24:18 PST 
Comment on attachment 302067 [details]
Patch

Clearing flags on attachment: 302067

Committed r212610: <http://trac.webkit.org/changeset/212610>
Comment 4 WebKit Commit Bot 2017-02-18 23:24:25 PST 
All reviewed patches have been landed.  Closing bug.