When I use Cmd-P, it sets the project page to print, instead of of the details in the task page (which is what I want), unsure how to use Cmd-P to print the task page.
I tried the same thing on Safari and it works fine (that solves my problem).
There is an existing thread where other users have reported to experience the same behaviour and our Development Team is currently working on this issue. I’ve gone ahead and merged your post with this main thread to avoid duplications and to keep you posted in one place as soon as I have an update about it!
Thank you for your help Leroy! Have a great Wednesday!
Thank you for reaching out @Shmuel_Davidoff and sorry to hear your are experiencing this issue.
In order to investigate this issue can you please provide the following information?
Is your browser updated?
Are you able to see your PDF normally when using Cmd-P?
Are running into the same issue while using a different Browser?
Can you please share a screenshot of the Print preview?
@Natalia can you by any chance find out what your engineering team did to resolve this issue, we’re having the same problem with our application and we’re at a loss how to fix it. Your help would be greatly appreciated. This has nothing to do with Asana but we’ve been on Asana for about 4 years now and really love the tool.
@Aaron_Kirley, @Natalia, @Marie, I have the same question, and had asked it in another thread, which I think should be combined with this one if they are in fact the same issue:
Actually - i have this issue in my own application www.lugless.com, it has nothing to do with Asana. I’m just wondering how Asana fixed this issue so we can attempt to apply the same fix www.lugless.com.
Hi! I’m the Asana engineer who worked on this issue.
It’s a pretty weird bug. What I found was that Chrome, on MacOS Catalina, would produce this garbled text if (a) the text was styled with system fonts and (b) anywhere on the page there existed some text from (a) that had font-style: italic.
All of those conditions were required to trigger the issue. Our workaround was to …remove some italics we were always displaying in our print view. (Yeah, not great.)