W3C home > Mailing lists > Public > www-svg@w3.org > August 2006

Re: should element with focus be within client window?

From: Jonathan Chetwynd <j.chetwynd@btinternet.com>
Date: Sat, 26 Aug 2006 11:46:23 +0100
Message-Id: <8F18D5CF-950C-4F6E-A963-753B86D1BCAD@btinternet.com>
Cc: Doug Schepers <doug@schepers.cc>, T Rowley <tor@cs.brown.edu>
To: www-svg@w3.org

Doug and Tim,

you appear to be describing a different issue.

the issue is that when using the keyboard (tabbing) with html, when  
focus moves to an element outside the client window, the application  
moves the element into the client window so it can be seen.
thus the element in focus is always in view.
(Obviously the mouse user can move an element in focus outside the  
window in many instances.)

Currently no SVG UA has this behaviour afaik.

My question is whether the current standards ensure that this  
behaviour in html is replicated with SVG.

Please note well that this is a very different issue from providing  
the means to search for the area currently in focus.

cheers

Jonathan Chetwynd



On 23 Aug 2006, at 20:00, Jonathan Chetwynd wrote:


should element with focus be within client window?

how do people navigating SVG using the keyboard know which element  
has focus?

for example: using mozilla, opera, safari-webkit etc visit
http://www.peepo.com/index-html-svg.html
zoom until a single graphic fills the page
then tab through the links.

each graphic with focus fills the client window in turn.

Contrast this with http://www.peepo.co.uk/index.svg

in each case apart from the initial graphic the user will have no  
idea which graphic has focus, due to the focus being outside the  
client window.

my apologies if this is in the spec. I do have recognised problems  
with the whole w3c process.

regards

Jonathan Chetwynd

mozilla zoom is currently disabled or broken..
Received on Saturday, 26 August 2006 10:46:36 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:35 GMT