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

Re: [css-overflow-3][css3-marquee][css3-gcpm] x/y directions (maybe [css3-break] too)

From: James Holderness <j4_james@hotmail.com>
Date: Thu, 11 Apr 2013 21:02:37 +0100
Message-ID: <BLU0-SMTP107ADE881D2CC86B995806BBEC00@phx.gbl>
To: "Brad Kemper" <brad.kemper@gmail.com>, "Morten Stenshorne" <mstensho@opera.com>
CC: Håkon Wium Lie <howcome@opera.com>, "Florian Rivoal" <florian@rivoal.net>, "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. 
> I
> should be able to author those properties to those values and be done with
> it. The UA could treat the transitions between x-overflowed pages
> differently from y-overflowed pages, but it wouldn't need to. Personally, 
> I
> think if there was a page curl animation between pages, then it should be
> the same for x as y overflowed: it's just a big stack of ordered pages. If
> the animation is more of a scrolling page-to-page effect, as Håkon 
> imagined,
> then a two axis animation of pages pushing each other out of the way might
> be more appropriate for the two types of overflow. Or all pages could push
> up from the bottom.
> 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>]*').

OK, this makes a lot more sense to me now. But I would still like the option 
of specifying an axis for some of those page-transitions if appropriate 
(e.g. something like slide-left vs slide-up - terrible names but you get the 

That way I can generate pages by overflowing horizontally with 
overflow-x:paged, but still have the option of transitioning vertically 
between those pages with page-transition:slide-up (or whatever).

Received on Thursday, 11 April 2013 20:03:16 UTC

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