W3C home > Mailing lists > Public > www-svg@w3.org > November 2004

SVG 1.2 Comment: Application Development

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Thu, 25 Nov 2004 00:01:12 -0600
Message-ID: <41A57528.3060704@mit.edu>
To: www-svg@w3.org

15.1.1:

Will making an element focusable allow it to match :enabled/:disabled?  If so, 
whether an element is focusable or not cannot be a property (since property 
values need to be calculated after the CSS cascade has been completed).  Note 
that several CSS proposals have had this same issue.  Perhaps this specification 
should explicitly say that the focusable property does not affect matching of 
:enabled/:disabled?

What happens when the element that has focus is modified via the DOM?  Say 
removed from the DOM tree?  Does the nearest ancestor still in the DOM tree get 
focus, the "next" element that can be focused get focus, the document get focus, 
or something else?

15.1.3:

next() and previous() are not names that are obviously associated with focus... 
perhaps focusForward() and focusBackward() or some such would be more appropriate?

"interface has", not "interface have"

15.2.1:

What happens when a hint element contains non-text content?

What happens if the text content of the hint element is empty?  Should a tooltip 
with no text be shown?  Should the parent's tooltip be used?

-Boris
Received on Thursday, 25 November 2004 06:03:30 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:14:53 UTC