search

ucsc / wcms-design-templates

Styles and Javascript for official UC Santa Cruz web templates
http://webassets.ucsc.edu
4 stars 4 forks source link

Printed pages need URL and print date in footer #345

Closed dajoturner closed 9 years ago

dajoturner commented 10 years ago

Christina Navarro reported this issue (INC0205133). Was there a reason not to include address and date on prints?

Christina said: The page prints with the content, but the print version no longer shows the url for where it was printed from and the date. I think that was useful information and would ask that be included in the programmed print layout.

thomasgardner commented 10 years ago

I believe this is a browser specific issue. I just tested this with both Firefox and Safari. In Safari one is given the choice to "Print Headers and Footers" i.e. screen shot 2014-09-17 at 3 36 40 pm When you select the check box to Print Headers and Footers the URL, date, etc is printed. If you don't select this check box it does not print. Firefox also offers a choice, i.e. screen shot 2014-09-17 at 3 37 22 pm

dajoturner commented 10 years ago

Good catch Tom. I tested on Chrome too, and it's the Headers and Footers option. Closing this, unless Christina comes back with a problem.

thomasgardner commented 9 years ago

Users are reporting that they cannot get the Date and URL to print, see INC0208364 My testing shows printing does not work using Google Chrome.

dajoturner commented 9 years ago

Setting this to Critical because of the client impact.

dajoturner commented 9 years ago

@knice I still have an open incident for this, and I know that it's important to a lot of our users. Can you update this issue with your current thinking - can we get this done, or does it need to go to services for future work?

knice commented 9 years ago

This has been fixed and the updated has been deployed to production. Confirmed in Safari, Firefox, and Chrome (latest releases, Mac OS only), headers and footers appear and do not interfere with page content.

This was fixed using the @page CSS at-rule

chrome-headers-footers

dajoturner commented 9 years ago

Woo hoo! Thanks Rob