It should be remembered that our current proposal does not solve all event
problems, so we are really deciding how much Web content adds event
handlers programmatically. If it is not much, why require a lot of
developer hacking that we will ask them to stop using in the future, if DOM
provides what we need in the future. We should do our best to get what can
be achieved now through the DOM and try to work with the DOM group to get
what we need in the future.
Jon
At 12:51 PM 3/8/2001 -0500, Charles McCathieNevile wrote:
>On Thu, 8 Mar 2001, Ian Jacobs wrote:
>
> Charles McCathieNevile wrote:
> >
> > If UAs don't keep track of the information, they will have a hard
> time making
> > use of it.
>
> The DOM API lets you add handlers, trigger them, and remove them,
> so the UA can do useful things through that interface even without
> keeping a list of the handlers available.
>
> -Ian
>
>Err, yes. But the question is "How can users discover things that have
>associated behaviour?" Which becomes interesting when they only have it
>sometimes - under what conditions does the user need to know where they are?
>
>Cheers
>
>Chaals
Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Division of Rehabilitation - Education Services
MC-574
College of Applied Life Studies
University of Illinois at Urbana/Champaign
1207 S. Oak Street, Champaign, IL 61820
Voice: (217) 244-5870
Fax: (217) 333-0248
E-mail: jongund@uiuc.edu
WWW: http://www.staff.uiuc.edu/~jongund
WWW: http://www.w3.org/wai/ua