Fwd: [css3-gcpm] new draft -- including "overflow: paged"

I'm not sure that I disagree with you, but I'd like to hear more about
> your reasoning. Why can't we just say that the viewport is the limit
> and no scrollbars will be provided?


I was thinking especially of document-viewer-like user interface (something
similar to Acrobat Reader plugin in windows), allowing the UA to instantly
jump to pages or bookmarks instead of jumping according to fragment
identifiers (so you write once for both print and screen)


>
> Opera, in its projection mode, allows content to grow but no
> scrollbars will be provided. You can use arrow keys and PgDn/PgUp to
> access all of (say) a large image. Here's a test document, press F11
> in Opera to see the effect:
>
>  http://people.opera.com/howcome/2009/operashow/test.html
>
> However, we *could* scale or crop the image and thereby enforce the
> viewport size. That would often create a better user experience.
>

The example you gave is actually the same user interface and rendering model
as normal viewing, w/o scrollbars. Something like
::viewport { overflow:visible; } instead of { overflow:auto; }
(assuming a fictional viewport pseudo element)

So
- if you want to split content into navigable pages, you may need to define
the size of a page (thus the @page applied to non-paged media) or define
what goes in which page, so that the UA can render a paged presentation,
although it may show pages flowing instead of individually

- If instead you just want to keep the current non-paged rendering model
while enforcing the viewport, you can use position: fixed; on the root
element, with top / left / bottom / right : 0px
In this way you can resize also vertically; horizontal constraining needs
even less work since horizontal percentage width is always relative to
parent width, and default is 100% of viewport


In other words, I don't understand what you actually mean

Giovanni


PS: sorry I forgot to include the list