15428 2012-01-05 14:26:21 +0000 :read-write should always apply to input elements if @readonly doesn't apply 2016-04-18 21:00:42 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified All All RESOLVED MOVED P2 normal --- 1 mounir chaals chaals ian jonas mike public-html-admin public-html-wg-issue-tracking robin tantek travil public-html-bugzilla oldest_to_newest 62298 0 mounir 2012-01-05 14:26:21 +0000 Given that the reasons why bug 13390 isn't going to be fixed means the widgets can't be read only I guess it would make sense to have :read-write applying to them. However, some of the input types for which @readonly doesn't apply shouldn't be considered :read-write like hidden, button, submit and reset. The ones that should be :read-write are: range, color, checkbox, radio and file. I think the specs should add as a second item after: "The :read-write pseudo-class must match any element falling into one of the following categories:" (4.14.2, ":read-write"), the following case: "input elements to which the readonly attribute does not apply and with a value mode different from value." If the value mode seems wrong, we could list the types for which it applies or the types for which it doesn't. 63612 1 ian 2012-02-02 21:54:14 +0000 IMHO neither should really apply to them, but the way I read CSS3 UI every element should match one or the other. 63631 2 Ms2ger 2012-02-03 09:33:42 +0000 Should we change CSS3UI? 70095 3 contributor 2012-07-18 06:53:38 +0000 This bug was cloned to create bug 17812 as part of operation convergence. 72232 4 Ms2ger 2012-08-15 17:13:33 +0000 Filter on [Idon'tcareaboutHTMLWGbugspam]. 125892 5 travil 2016-04-18 21:00:42 +0000 HTML5.1 Bugzilla Bug Triage: Moved to https://github.com/w3c/html/issues/215. If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks!