New print window and custom print style

Message received, we’ll provide a full response and help with a permanent solution in the coming days.

Just checking back in on this. Please let us know if this is going to be solved.

the work we put into the custom print page style for these many assets is now useless. So, we’ve reverted back to 1.7 as you’ve noted for all these assets.

To be clear, the current method of using @media print CSS to define how a print is styled will remain. The old method of ‘cloning’ the targeted print CSS into a new window and then loading in custom CSS will not return in the current or future versions.

That being said, the described use case of printing eBooks and whitepapers that have a different print style (and perhaps layout?) than the display versions might benefit from a custom print template offered in Print-Pro-Matic. This would allow for a complete custom print-only-version, complete with it’s own CSS to be used when the print is triggered.

If this is not interesting, then it would be best simply to stick with version 1.7.x with it’s pop-up print window and custom print-only css that is not based on the Theme CSS. However, anything that could have been accomplished with CSS using version 17.x can be recreated using the 2.x versions, it’s just that perhaps more display CSS would need to be re-defined/overwritten if the display CSS interferes too much with the desired print style.

I saw a development note that you guys added back the printomat.js code in 2.1.1? Does this mean the previous print page functionality should be back?

No.

Also, if we do use this @mediaprint approach, I’m trying to figure out why we need POM at all since that can be done with standard CSS.

Print-O-Matic adds control over the page elements that are to be printed–or not printed.

I trust that this provides a detailed enough response to your query. Do let. us know if you have more questions or if we can be of and further assistance.