13931 2011-08-28 16:15:41 +0000 Why are editable inputs/textareas not :read-write? 2011-10-24 14:49:21 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other CLOSED INVALID http://www.whatwg.org/specs/web-apps/current-work/#pseudo-classes P3 normal --- 1 contributor ian ayg ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 55935 0 contributor 2011-08-28 16:15:41 +0000 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 55939 1 ayg 2011-08-28 16:16:27 +0000 *** Bug 13932 has been marked as a duplicate of this bug. *** 55941 2 ayg 2011-08-28 16:16:44 +0000 *** Bug 13933 has been marked as a duplicate of this bug. *** 55942 3 ayg 2011-08-28 16:19:18 +0000 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.) 58137 4 ian 2011-10-12 19:27:01 +0000 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. 58748 5 ayg 2011-10-24 14:49:13 +0000 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.