- From: Anne van Kesteren <annevk@opera.com>
- Date: Sun, 25 Jun 2006 12:59:15 +0200
- To: public-cdf@w3.org
On Sun, 25 Jun 2006 12:54:56 +0200, Timur Mehrvarz <timur.mehrvarz@web.de> wrote: >>> WICD Core assumes identical treatment, for as long as (scalable) child >>> elements are not explicitly made focusable. >> >> Could you please elaborate on "explicitly made focusable"? > > How about.. > > "For a child element to become focusable, it must advertise itself as > being focusable." > > Agents should make child elements explicitly focusable, only if they > require focus. (If they are interactive or contain links or whatever.) > Elements that do not require focus (such as bitmap images and non > interactive SVG) should - by default - not receive focus. So I agree it would be if all UAs followed the same model and I hope they do so for the majority of the cases, but we shouldn't prevent UAs from coming up with alternative (default) UIs if they so desire. I guess a RFC 2119 SHOULD would cover that, but I'm not entirely sure. > With this, authors can make use of bitmap images and non interactive SVG > elements, purely for style purposes. Without bringing down the usability > of their documents at the same time. > > Agents may, of course, provide an alternative rendering mode, in which > also non interactive SVG elements become focusable. But this should then > probably also include bitmap images. (Btw, this is meant by "child > elements must be treated like bitmap images". Not sure if this answers > your question.) The problem I have with "child elements must be treated like bitmap images" is that it seems to assume some default treatment for bitmap images that isn't really clear from the text. -- Anne van Kesteren <http://annevankesteren.nl/> <http://www.opera.com/>
Received on Sunday, 25 June 2006 10:59:33 UTC