Re: [xwiki-devs] [Proposal] Using the browser's print feature instead of our PDF Export for the UI

I’ve just tested it and I could select the orientation, paper size, margins, whether header/footers are printed, etc. Well that’s the problem and the reason why I sent this email: right now FOP doesn’t allow us to control much because it’s limited and buggy. We have plenty of open jira issues related to FOP and we’ve worked hard (too hard) to fix issues in the past and we’re stuck on several of them (I can think of table auto layout). When I’ve tried to export a wiki page both with the browser print button and with our PDF export, I’ve had a better result (by better I mean that corresponds more to what the user is viewing) with the browser print button. Of course our print.css is lacking a lot of styles but that’s easily fixable (BTW I don’t understand why we don’t use view styles by default, most of them should work just fine). The other advantage is that browsers work all the time to improve this and thus we delegate the work to them (we reduce our maintenance). Note that I’m not suggesting to drop what we’re doing now but to not make it the default since it’s of lower quality than the browser print result. What we could do right now is: * Run some factual tests on various wiki pages and compare them with both solutions and see which are best. * Quickly try to improve our print.css to match our style.css more. Thanks -Vincent