W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > July to September 2009

Web Based User Agent - further

From: Simon Harper <simon.harper@manchester.ac.uk>
Date: Fri, 28 Aug 2009 16:08:46 +0100
Message-Id: <C9B20245-3264-4AA2-B11E-2D007B1C45D0@manchester.ac.uk>
To: UAWG list <w3c-wai-ua@w3.org>
OK so firstly on input it seems to be possible to capture keystrokes  
and not pass them on (with an
event listener that calls event.preventDefault();) - this is in  

Further, we've found that we cannot control how other scripts (part  
of the page) handle keystrokes.  For example, with auto-suggest  
lists, there is typically an event handler on the page that listens  
for the return key, and completes the box with the highlighted  
value.  We want the return key to enter the user's selection (which  
is not necessarily highlighted), but we can't make the return do what  
we want first time - the only way round it is for the user to hit  
return twice.

Now output, we've not tried making changes without triggering a  
DOMMutationEvent, but it sounds tricky.  The only way we can imagine  
is by removing all DOMMutation event listeners (if this is possible),  
making the change, then adding them again. However, if we are not  
changing the DOM but communicating via just the appearance (i.e.,  
something that could be achieved by changing the CSS only), then this  
could be possible, as could interfacing to drawing apps or pushing  
anything in the new html5 canvas.



Simon Harper
University of Manchester (UK)

Human Centred Web Lab: http://hcw.cs.manchester.ac.uk

My Site: http://hcw.cs.manchester.ac.uk/people/harper/

My Diary (Web): http://hcw.cs.manchester.ac.uk/people/harper/ 
My Diary (Subscribe): http://hcw.cs.manchester.ac.uk/diaries/harper/ 
Received on Friday, 28 August 2009 15:09:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:38:40 UTC