W3C home > Mailing lists > Public > www-style@w3.org > April 2015

[css3-ui] directional nav error handling

From: Florian Rivoal <florian@rivoal.net>
Date: Fri, 10 Apr 2015 17:36:17 +0200
Message-Id: <6C35A38F-74A5-48A7-8544-D2F3E85958AE@rivoal.net>
Cc: Tantek Çelik <tantek@cs.stanford.edu>
To: www-style list <www-style@w3.org>
I found something that needs clarification in the directional navigation

  The <target-name> parameter indicates the target frame for the focus
  navigation. It is a <string> and it cannot start with the underscore
  "_" character. If the specified target frame does not exist, the
  parameter will be treated as the keyword current.

It cannot start with an underscore character, but what happens if it does is
unclear. I think we should explicitely pick one of these:

a - This is an author level requirement, so using it is invalid, but the
    behavior is defined, and if there is a frame by that name that doesn't
    conflict with one of the reserved keywords (although that's a spec
    violation), the UA must navigate to it anyway.

b - Same as a, but in addition, "_parent" and "_top" navigate to the parent
    and root frame, respectively.

c - This is an author level requirement, so using it is invalid, and the
    behavior is undefined.

d - treat as the current frame (same behavior as for non existing frame

e - Parse error

Presto does a.
The Samsung chromium implementation does b.
e sounds like handling this at the wrong layer.

I think I prefer b. It is invalid, but having interoperable error
handling is good, and the author intent is clear.

If we want to prioritize spec advancement over interop, we could do c in
level 3, and go for b in level 4.

Side note: If you're trying to test spatial navigation in various browsers,
and can't remember how to activate it or which keys to use, I've made a blog
post about that:

 - Florian
Received on Friday, 10 April 2015 15:36:41 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:50 UTC