W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2000

RE: Seeking guidance...

From: Bruce Bailey <bbailey@clark.net>
Date: Fri, 7 Apr 2000 11:43:41 -0400
To: <w3c-wai-ig@w3.org>
Cc: "Christopher Atkinson" <cwa@pipeline.com>, "Charles McCathieNevile" <charles@w3.org>, <cpl@starlingweb.com>
Message-ID: <000a01bfa0a8$0c5f8640$53fe330a@msde>
Charles McCN wrote:
> No, onFocus (in the current specification) does not replace onMouseover in
> current versions of HTML (sadly).
>
> In the upcoming DOM work, there is a new focusin/focusout event that is
> expected to cover mouseovers as well as keyboard-based focus.

Okay then, MSIE5's behavior wrt onFocus/onBlur is reasonable.

Chuck L wrote (earlier in this thread):
> However, I feel strongly that page developers should (must) get into the
> habit of enabling device independent triggers on all suitable scripts in
> spite of the problems with the current crop of event-handlers noted
earlier
> on the IG list.

Aside from agreeing with this in principle, what is the point?  The current
formal SPECIFICATIONS don't even adequately support this mindset!
(Forgetting, for the moment, the behavior of the UA browser.)

Let me ask again, do any of the keyboard-oriented tags (onKeyPress,
onKeyDown, onKeyUp) substitute adequately (from a functional keyboard
orientation) for onFocus/onBlur?

--
Thank you.
Bruce B
Received on Friday, 7 April 2000 11:46:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:13:48 GMT