On Fri, 28 Nov 2008, Anne van Kesteren wrote:
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
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
On Mon, 16 Jun 2008, Adele Peterson wrote:
In HTML5, focus() and blur() are now defined on HTMLElement instead of
being restricted to specific form elements.
In Web Forms 2.0, the autofocus attribute is defined for any form
control (except hidden and output controls). It seems like it
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
In HTML5, focus() and blur() are now defined on HTMLElement instead of
being restricted to specific form elements.
In Web Forms 2.0, the autofocus attribute is defined for any form
control (except hidden and output controls). It seems like it would
make more sense to allow autofocus to be
On Mon, 16 Jun 2008 21:17:18 +0200, Adele Peterson [EMAIL PROTECTED] wrote:
In HTML5, focus() and blur() are now defined on HTMLElement instead of
being restricted to specific form elements.
In Web Forms 2.0, the autofocus attribute is defined for any form
control (except hidden and output
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
