W3C home > Mailing lists > Public > www-style@w3.org > October 2011

Re: [css3-gcpm] paged presentations, page floats, paged navigation between documents

From: Nicholas Shanks <contact@nickshanks.com>
Date: Sat, 15 Oct 2011 18:27:06 +0100
Message-ID: <CA+hEJVWBG--NhX5PK-5jUcrH=aFWqCAow_w0jv+nVZJzuYV2gQ@mail.gmail.com>
To: Håkon Wium Lie <howcome@opera.com>
Cc: www-style@w3.org
On 15 October 2011 14:20, Håkon Wium Lie <howcome@opera.com> wrote:

> 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.

Understood. I just fear that adding support for (and ratifying) a new
CSS @-block will be slower than the integration of gesture support
into browsers on Metro/iOS/Android/etc. platforms.
It would still be useful for you to collaborate on finding good
defaults that all browsers can agree to, in terms of
gesture-to-link-relation mapping, which can go into code or the UA
stylesheet once @navigation is implemented, and those defaults
advertised so people can avoid overriding them with identical values!

-- 
Nicholas.
Received on Saturday, 15 October 2011 17:35:22 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:45 GMT