This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#pseudo-classes Complete: http://www.whatwg.org/c#pseudo-classes Comment: Why are editable inputs/textareas not :read-write? They Posted from: 68.196.183.196 User agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.861.0 Safari/535.2
*** Bug 13932 has been marked as a duplicate of this bug. ***
*** Bug 13933 has been marked as a duplicate of this bug. ***
They seem no less editable than, say, an editable <img> or <hr> or whatever. You should be able to delete them or move them around. (The editing spec doesn't yet define this, but at the face-to-face we agreed that form stuff should be meaningfully editable: the user should be able to edit the values and so on. This allows form-editing apps. If authors want an input to be non-editable and thus behave like an actual input, they can specify contenteditable=false.)
They are :read-write unless they're <textarea readonly> or disabled or similar. Are you saying you want disabled or read-only <textarea>s and <input>s to be :read-write? It seems like that would cause authors to unexpectedly give such form controls the "wrong" style when editing.
Hmm, okay. It's kind of confusing, but I guess that's inevitable. I withdraw the request -- I'm no longer confident the spec's behavior is wrong.