Bug 46562
Summary: | Support repeating elements - CSS Generated Content for Paged Media Module | ||
---|---|---|---|
Product: | WebKit | Reporter: | dev_oskar |
Component: | Printing | Assignee: | Nobody <webkit-unassigned> |
Status: | UNCONFIRMED | ||
Severity: | Enhancement | CC: | prasanna.a.venkatesh, tpopela, webkit.org |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | PC | ||
OS: | All |
dev_oskar
Support for reposition and repeating of elements in the document flow for printing should be supported,
This way a header and/or footer elements can be moved into the CSS3 Paged Media Level 3 Margin Boxes.
CSS3 Paged Media Level 3 lacks the concept of reposition of elements.
CSS Generated Content for Paged Media Module - Running headers and-footers
( http://www.w3.org/TR/css3-gcpm/#running-headers-and-footers ) adds the concept of reposition of elements via css.
PrinceXML supports reposition via the "prince-flow" property.
If "Running headers and footers" will be to complex to add webkit rendering,
Webkit could at least add a way to reintroduce an element into the document flow on each printout page.
A simple approach would be a new prefixed css property:
-webkit-position-repeat: none;
-webkit-position-repeat: top;
-webkit-position-repeat: bottom;
Adding enough room for bottom elements is tricky.
An approach could be to reduce the virtual page size, as soon as a page break page should happen, the bottom element(s) get added and rendered.
This concept may be useful for thead/tfoot printing on each page too.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
prasanna.a.venkatesh
Yes, this is becoming a serious issue. I feel sad for proposing Chrome to the client. This feature is letting us down and is a must to have a fix.