- From: Ian B. Jacobs <ij@w3.org>
- Date: Mon, 09 Jul 2001 13:13:30 -0400
- To: Jon Gunderson <jongund@uiuc.edu>
- CC: Tantek Celik <tantek@cs.stanford.edu>, w3c-wai-ua@w3.org
Jon Gunderson wrote:
>
> With event bubbling model used for scripting, every element potentially can
> be interactive.
No, potentially "enabled".
> The user agent can make pretty good assumptions from the
> markup that elements with an "on" event hander, marked up as a link or
> input controls is an interactive element. Other elements maybe interactive
> based on scripting, which is difficult or impossible for the user agent to
> determine from markup. Maybe the term non-interactive needs to defined in
> terms of "recognized through markup".
I think the document is already sufficient on this front.
1) The definition states:
"A non-interactive element is an element that, by specification,
does not have associated behaviors."
It is thus only by virtue of specification (whether markup language
or
style sheets) that something would be considered interactive or
non-interactive.
2) The applicability provision is always in force anyway. So if not
recognized, it
doesn't apply.
_ Ian
--
Ian Jacobs (ij@w3.org) http://www.w3.org/People/Jacobs
Cell: +1 917 450-8783
Received on Monday, 9 July 2001 13:16:41 UTC