In my view, onfocus and onblur events are not used in ways destructive to accessibility. Perhaps someone can prove me wrong. I also think it's putting a big burden on developers, and the complexity of the UI, to support navigating to elements without focusing there. Personally, if we can't find a real world example, I'd like to see onfocus and onblur events excluded from the bit about needing to navigate without setting off event handlers. Unless someone can argue a good case where it's really useful. Aaron jon gunderson wrote: > Does any body have any information on the current use of onFoucs and > onBlur events? > > Jon > > > On Fri, 9 Mar 2001, Aaron Leventhal wrote: > >> Can anyone find a real world example where the automatic onfocus that's >> called is something you don't want automated? >> BTW, thanks to Gregory for the example (albeit strange) of the >> destructive this.close() call. >> >> Aaron >> >> >> -- >> For information about Netscape and Mozilla Accessibility projects, >> please see the Access Mozilla <http://access-mozilla.sourceforge.net> >> website. >> To join the mozilla-accessibility mailing list, send email to >> mozilla-accessibility-request@mozilla.org <mailto:mozilla-accessibility-request@mozilla.org> >> <mailto:mozilla-accessibility-request@mozilla.org?subject=subscribe>, >> subject "subscribe". >> >> -- For information about Netscape and Mozilla Accessibility projects, please see the Access Mozilla <http://access-mozilla.sourceforge.net> website. To join the mozilla-accessibility mailing list, send email to mozilla-accessibility-request@mozilla.org <mailto:mozilla-accessibility-request@mozilla.org?subject=subscribe>, subject "subscribe".Received on Tuesday, 13 March 2001 03:12:30 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:50:38 GMT