Re: Responses to Tantek Çelik issues raised during third last call of UAAG 1.0

From: "Ian B. Jacobs" <ij@w3.org>
Subject: Re: Responses to Tantek Çelik issues raised    during  third  last
call of UAAG 1.0
Date: Mon, Jul 9, 2001, 10:13 AM

> 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

The word "specification" is ambiguous in this context.

Does it mean "specified by an author or user"?

Or does it mean W3C specification?

It could easily mean either, and have very different impact upon the
definition.

> (whether markup language
> or style sheets)

or script (programming) for that matter.

> 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


Tantek

Received on Monday, 9 July 2001 13:32:35 UTC