On Sat, 08 Nov 2008 18:46:48 +0100, Ian Hickson <[EMAIL PROTECTED]> 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?
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
