- From: Håkon Wium Lie <howcome@opera.com>
- Date: Sat, 15 Oct 2011 15:20:53 +0200
- To: Nicholas Shanks <contact@nickshanks.com>
- Cc: www-style@w3.org
Also sprach Nicholas Shanks:
> > The @navigation rule is used to position other documents around the
> > current document. This way, user gestures can be used to navigate to
> > the. As such, the "point-and-click" metaphor of the web is extended
> > with "navigate-through-gestures". E.g.:
> >
> > <link rel=index href="...">
> > <link rel=next href="...">
> >
> > @-o-navigation {
> > nav-up: -o-link-rel(index);
> > nav-right: -o-link-rel(next);
> > }
>
> I haven't seen anyone else comment on this section, but I think your
> @navigation block is not necessary, as it just adds an extra layer of
> abstraction/indirection. What you are trying to do appears to be to
> allow web developers to control the mapping between a UA-provided
> semantic navigation event, and a HTML-specified spacial relation
> between resources, implicitly implying that navigation to that
> resource is to occur in response to the event. I think such a mapping
> should be defined by the user agent itself, or allow the user to set
> the corresponding relation (from the set of HTML rel attribute values)
> for each gesture available (with co-ordinated defaults).
I agree that users and browsers also should be able to make such
settings. This fits well into the CSS model of cascading; style sheets
may come from different sources. There's nothing author-specific about
@navigation, and you could also put the code snippet abov into your
personal style sheet.
I do think, though, that it's important to allow authors to express
their preferences. Otherwise, they will use other mechanisms --
mechanisms that cannot easily be overriden by users.
Cheers,
-h&kon
Håkon Wium Lie CTO °þe®ª
howcome@opera.com http://people.opera.com/howcome
Received on Saturday, 15 October 2011 13:21:37 UTC