Quote:
Originally Posted by dgatwood
In theoretical future readers that support all of CSS3, you might be able to to this:
Code:
img { move-to: page-top; }
|
That looks nice, but a closer look at the
CSS3 working draft reveals that it wouldn't work as expected, even if it were supported.
The example says:
Code:
img { move-to: page-top; } /* move images to page-top */
@page { padding-top: 10em; } /* leave a gap at the top of the page */
body:after { /* place a box at the top of each page */
position: fixed; top: 0; left: 0; right: 0; height: 10em;
content: pending(page-top); /* insert the images moved to page-top */
}
"page-top" is not some special keyword, it's just an identifier, it could say "foobar" instead, so the img is simply moved to wherever we specify "pending(page-top)", and I don't see how we could say we want it at the next (or current) page top. Reading the rest of the example (@page and body:after), what is actually achieved, if I'm not mistaken, is that
all images in the document are collected and placed at the top of
every page, and with absolute positioning, which required adding manual padding.