- From: Ian Hickson <ian@hixie.ch>
- Date: Tue, 2 Dec 2008 11:01:50 +0000 (UTC)
On Fri, 28 Nov 2008, Anne van Kesteren wrote: > On Sat, 08 Nov 2008 18:46:48 +0100, Ian Hickson <ian at hixie.ch> wrote: > > On Mon, 16 Jun 2008, Adele Peterson wrote: > > > I saw the need for this in our Web Inspector, which has a lot of custom > > > controls (including some that use contenteditable elements). Some of > > > these don't have a default focused appearance, but its nice that they > > > can follow the focus pseudo-class CSS selector. > > > > > > I agree that the disabled attribute would fit in well with this. > > > Again, it would be nice for these custom controls to be able to use the > > > disabled pseudo-class CSS selector. > > > > I really would rather see XBL2's <div> element be extended to be > > focusable and disablable rather than have HTML support this. Does that > > make sense? > > How would you disable <td contenteditable> or <div contenteditable> with > that strategy and have td:disabled and div:disabled (or something very > close to it) work? It would require something similar to what I had in mind for the very neglected Web Controls 1.0 draft, i.e. an API that sets when an element is disabled or editable or whatever, that all the other attributes and form controls are defined in terms of. (This would also have been a better way of doing what ARIA does.) -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 2 December 2008 03:01:50 UTC