This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 15428 - :read-write should always apply to input elements if @readonly doesn't apply
Summary: :read-write should always apply to input elements if @readonly doesn't apply
Status: RESOLVED MOVED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Charles McCathieNevile
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-05 14:26 UTC by Mounir Lamouri
Modified: 2016-04-18 21:00 UTC (History)
9 users (show)

See Also:


Attachments

Description Mounir Lamouri 2012-01-05 14:26:21 UTC
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.
Comment 1 Ian 'Hixie' Hickson 2012-02-02 21:54:14 UTC
IMHO neither should really apply to them, but the way I read CSS3 UI every element should match one or the other.
Comment 2 Ms2ger 2012-02-03 09:33:42 UTC
Should we change CSS3UI?
Comment 3 contributor 2012-07-18 06:53:38 UTC
This bug was cloned to create bug 17812 as part of operation convergence.
Comment 4 Ms2ger 2012-08-15 17:13:33 UTC
Filter on [Idon'tcareaboutHTMLWGbugspam].
Comment 5 Travis Leithead [MSFT] 2016-04-18 21:00:42 UTC
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!