Is this css in a file, or directly in the form settings?
One troubleshoting trick to know the @Media is working is to set color:red. If the color doesn't change to red, then the issue isn't with the font inclusion.
adding color:red; to the @media print does not change the font red but if I change the color:red; outside the @media print type and straight to my .Signature class in the style sheet, the font prints red. seems the @media print type isn't needed if you want to print exactly what is displayed on the screen. My .Signature class now prints red but without the custom font. Any ideas?
Right, you only use the print media when you want the CSS to be different between the screen and paper. Are you testing this with print preview to see the changes, any print to paper tests? Is this what you are trying to accomplish?
setting color:red does nothing in the @media print type. I want the font used on the screen to be the same in the pdf. if I remove @media print all together I still get a different font then my @font face defined in my css which is directly in the settings of the form not a separate file. I have not printed anything to paper I want the .pdf file to have the same font that is in the nintex form on the screen.
thanks for taking the time to help.
The color:red should take, but one thing to clear up easily is that the following doesn't apply to you.
Unsupported form configuration for PDF rendering
Form Configuration | Discription | Browser |
Rules | Custom CSS rule @Media rule. | Only applies to Internet Explorer 8. |
Also, I can understand the font not working if a download of the font class is being imported at the time of rendering. Not sure if it is unsupported though.
Here are my results in a test in O365.
@media print { .tester {color:red;}} was put into the form settings custom css box.
On the control, I set the CSS class "tester" as so
When I view the form I see
When I hit print, I see
So then I added .tester {color:blue;} so it would be blue normally, then change to red when I print.
So it can work, maybe its the setup for you?
this doesn't apply. how do I import a custom font to work with print to pdf. We don't have to worry about media queries as I want the screen and pdf to be the same. All I want is a cursive font on screen and in my pdf. thanks
So here is the same testing but using font-face.
The form in edit mode that is displaying my font:
The PDF version of the same form showing the font working correctly:
Using Font-Face in custom CSS works in O365.
Ok, That shouldn't be any difference in how it works. Please compare the configuration with mine.
My font shows fine in the form using this method. It does not show up in the pdf.
Ok, that's too bad it doesn't show up. I think at this point it is best to create a support ticket with Nintex and see if it can be corrected. Let us know how they respond.
they wont support it:
Response from Nintex:
Thank you for your email, I understand that you're attempting to implement custom CSS in your form and you've found that this does not work as expected.
We unfortunately do not have the knowledge or resources to troubleshoot and support custom CSS, however our technical partners are better positioned to help you with this and would be more than happy to work with you on this.
I hope that you understand our position on this, but please do get back to us if you have any further questions on the above.
Kind regards,
I was able to get nintex to look at the issue and they have confirmed that custom fonts will NOT work in print to pdf for On-premise. The offered no solution to the issue stating "the development have reviewed this issue and have determined that the browser is overriding the CSS, hence why the custom font isn't used when the form is converted. Our development has also investigated if there is a workaround for this, but unfortunately, they've found this behaviour is controlled by the web browser and they are unable to override it."
Do we know which browsers (and versions) are affected by this? As I could not reproduce the issue in Chrome.
they said Firefox, Chrome and IE are affected. I am using Nintex On-Premise 2013 Version: 2.10.0.0