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

2011/10/12 Håkon Wium Lie <howcome@opera.com>
> David Hyatt wrote:
>  > >  html {
>  > >    overflow: paged-x;
>  > >    height: 100%;
>  > >    columns: 20em;
>  > >  }
>
>  > I like using overflow (Robert O'Callahan and I shared that idea in
>  > a discussion years ago), but it's a bit weird given that overflow
>  > is a shorthand. What does it mean to set overflow-y: paged-x? It
>  > seems to me that it should be sufficient to simply have a value,
>  > "paged" and the author can set it using the appropriate overflow
>  > property, e.g.,
>  >
>  > overflow-x: paged
>
> This is where Opera started. The current 'overflow: paged-x' was
> introduced to avoid making nonsensical statements like the one you
> mention: 'overflow-y: paged-x'. From the perpective of paged
> presentations, it only makes sense to set values on the shorthand
> 'overflow' -- not on 'overflow-x' or 'overflow-y', no?

Oh, I see.  You're specifically saying that overflow is paged in that
direction, not that overflow in that direction is paged.  So, which
direction of overflow becomes paged, the block or inline axis?  Or the
horizontal or vertical axis?  The fact that you used large columns in
your example implies that pages are always generated from the overflow
in the inline axis.


>  > I would not have separate overflow values for showing controls.
>  > Ultimately I think built-in controls are not going to be very
>  > popular for this and that people are going to want to roll their
>  > own. There's going to need to be some DOM API for this feature I
>  > think (to avoid making people have to do all the math to figure out
>  > where columns are and to have to count pages themselves).
>
> Opera has implemeted DOM access to the paged presentations, I attach a
> code example.

I presume you meant to attach a code example, and not just fill the
latter half of your email with lorem ipsum.  ^_^

~TJ

Received on Wednesday, 12 October 2011 15:09:46 UTC