Open Bug 286443 (css-paged-media) Opened 16 years ago Updated 7 months ago
[META] CSS Paged Media Module Level 3
Is there a plan to implement CSS3 Paged Media any time soon? It would be *very* helpful to be able to write books in XHTML/CSS rather than being forced to write them in SGML then convert them to the required formats (XHTML/PDF/TXT/...). Having control of the header/footer areas (as specified in CSS3) would give authors the ability to write cross-platform compatible documents without needing all the extra garbage to produce a PDF. Once that's done, I can tell my users to go to a web page to get a current copy of the book and print it if they wish knowing they'll get page headers and footers just like they've come to expect in my PDF's.
Component: Page Info → Style System (CSS)
Product: Firefox → Core
> Is there a plan to implement CSS3 Paged Media any time soon? Depends on what you mean by "soon". Probably not this year. See also bug 278678 and bug 189597. Chances are, these bugs should be dups or dependents of each other.
(In reply to comment #1) > > Is there a plan to implement CSS3 Paged Media any time soon? > > Depends on what you mean by "soon". Probably not this year. > > See also bug 278678 and bug 189597. Chances are, these bugs should be dups or > dependents of each other. Any updates on a possible time-frame for this?
FYI all - the reason I'm asking for this is pretty simple - I'd like to leave behind PDF, DOC, and other formats specifically set up for printing and start coding my printable documents in HTML/CSS. I'm sure I'm not the only one who would like to do this. That would mean one less huge complication on maintaining documentation by helping me get away from having to do docbook, then converting to printable formats.
*** Bug 339354 has been marked as a duplicate of this bug. ***
Assignee: dbaron → nobody
QA Contact: ian → style-system
Seconded! (In reply to comment #3) > FYI all - the reason I'm asking for this is pretty simple - I'd like to leave > behind PDF, DOC, and other formats specifically set up for printing and start > coding my printable documents in HTML/CSS. I'm sure I'm not the only one who > would like to do this. That would mean one less huge complication on > maintaining documentation by helping me get away from having to do docbook, > then converting to printable formats.
If Mozilla is thinking about incorporating an ePub reader, that project and this problem would fold into each other. ;)
Google Docs' printing feature now makes use of CSS3 Paged Media. Maybe this gives a little priority boost... See here: http://googledocs.blogspot.com/2011/04/pagination-comes-to-google-docs.html
(In reply to comment #7) > Google Docs' printing feature now makes use of CSS3 Paged Media. Maybe this > gives a little priority boost... > See here: > http://googledocs.blogspot.com/2011/04/pagination-comes-to-google-docs.html You should probably bring that up in the newsgroups as a lot of the devs read there.
"Depends on what you mean by "soon". Probably not this year." As I see, nothing happend in the last 6 years. I hope at least FF will fully support paged media in 10 years.
Firefox has a superb support for XHTML, SVG, and MathML. Complete support for CSS3 paged media is the only thing missing to make it perfect for creating professional books and print material. I hope this feature will be added soon.
I believe this bug report should use the meta keyword. And it did not depend on bug 115199.
People who want to help Firefox achieve CSS3 Paged Media support should start filing unique, distinct bug reports based on sections and features in latest version of the spec. It should be understood that the spec is in Working Draft and can still change. Such bug reports' summaries should start with "[CSS3 Paged Media]", have component field set to "Printing: Output" and be blocking this bug 286443 . Eg. [CSS3 Paged Media] support for margin at-rule (e.g. @top-left) How to Write a Proper Bug https://quality.mozilla.org/docs/bugzilla/starter-kit/how-to-write-a-proper-bug/ Bug writing guidelines https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines A good bug report starts with a clear, concise summary, a good description, formal expected results and formal actual results. Having a reduced test case will help tremendously. How to Really, Really Help Developers on Bugs -- Minimal Testcases https://wiki.mozilla.org/MozillaQualityAssurance:Triage#How_to_Really.2C_Really_Help_Developers_on_Bugs_--_Minimal_Testcases Reducing testcases: Why make reduced testcases?, How do I make a reduced testcase? https://developer.mozilla.org/en-US/docs/Reducing_testcases?redirect=no Note that page-break properties http://www.w3.org/TR/2012/WD-css3-break-20120823/ should be filed under another meta bug report. adding meta keyword Gérard
You need to log in before you can comment on or make changes to this bug.