- From: Florian Rivoal <florian@rivoal.net>
- Date: Thu, 11 Apr 2013 17:03:31 +0200
- To: "Morten Stenshorne" <mstensho@opera.com>, "Brad Kemper" <brad.kemper@gmail.com>
- Cc: "James Holderness" <j4_james@hotmail.com>, Håkon Wium Lie <howcome@opera.com>, "www-style list" <www-style@w3.org>
> The more I think about it, the more convinced I am that it is the job of
> 'overflow-x:paged' and 'overflow-y:paged' to only create the pages, not
> to decide for the UA what special effect is used for switching between
> pages.
>
> [...]
>
> The point is that deciding the mechanism and animation for moving
> between pages is really a separate problem from deciding how to turn
> overflow into pages. There should at least be a default way of animating
> and actuating that change that is independent of just setting
> 'overflow-x:paged' and 'overflow-y:paged'. In Flipbook for iPad, the
> pages flip to the left, and in Flipbook for iPhone, they flip up. In
> iBooks, the pages curl to the left in one mode, and push up from the
> bottom in another mode. In Kobo, the user can set the "page transition
> style" to either a page curl or a page fade. If we wanted to give
> authors this capability, we could have either an @rule as I previously
> described, or as a separate inheritable property ('page-transition:
> [none | fade | curl | push | slide-reveal | <custom-animation>]
> [<speed>]*').
This makes a lot of sense to me.
Received on Thursday, 11 April 2013 15:03:55 UTC