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

> Note that Opera's implementation uses overflow-x and overflow-y, as they 
> are longhands on overflow, and get the values from it.
>
> http://www.opera.com/docs/specs/presto2.11/paged-overflow/
>
> This is different from what was specified in GCPM, which uses 
> overflow-style.

I've been experimenting with the Opera implementation a little, and I'm not 
sure I fully understand how it is supposed to work.

If I create a block with a fixed width and height, and enough lines of text 
that would overflow the height of that block, setting overflow:paged-x lets 
me view the vertical overflow by paging horizontally, and overflow:paged-y 
lets me view the vertical overflow by paging vertically. That's all great.

However, if instead of overflowing vertically, I create a long line of text 
with no spaces that would typically overflow horizontally, none of the paged 
overflow settings seem to have any effect. I would expect something like 
overflow:paged-x to work similarly to overflow-x:scroll (only paged) but it 
doesn't.

Is this something that's just not supported? Does paged overflow only apply 
to content that overflows vertically or is there something else I'm doing 
wrong?

In an ideal world I would like to have content that overflowed both 
vertically and horizontally and then set overflow-x:paged-x and 
overflow-y:paged-y, resulting in a virtual grid where you could page both 
vertically and horizontally to pan across all the available content. Is that 
wishful thinking?

Regards
James

Received on Wednesday, 10 April 2013 15:33:08 UTC