-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Printing on Google Slides doesn't work with Shields up #26079
Comments
cc: @ryanbr Looks like the print dialog show up ok with Shields down. Only an issue on Google Slides. Works fine (print dialog shows up) with Sheets and Docs with Shields down. |
@rebron - regarding the label "workaround/shields-down"; does this label mean it will not be properly fixed, i.e as there is a workaround? |
@twMat Only means that there is a workaround. We want a proper fix for it. |
Looks like a fingerprinting issue, Allowing fingerprinting on |
Sorry, but I am having this problem now and shields down is not helping. I can confirm printing works normally on Sheets, but not on Slides. |
"plugins" fingerprinting. |
Print preview now working |
Well, still not for me. Turning shields off makes it work. |
Maybe check in a new profile? |
Description
We had an old issue for Google services where Brave would force the user to save the [content] as a
.pdf
rather than initiating the print screen dialog:#3694
This issue seems to have reappeared specifically for Google Slides. Attempting to print anything on Slides with Shields up forces the user to save the content as a
.pdf
. Attempting to print w/ Shields down displays the print screen dialog as intended:Screen.Recording.2022-10-17.at.11.45.38.AM.mov
Steps to Reproduce
.pdf
Reproduces how often:
Always
Brave version (brave://version info)
v1.44.112
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
User report:
https://community.brave.com/t/bug-missing-print-dialogue-in-google-slides-only-save-as-pdf/429045/14
The text was updated successfully, but these errors were encountered: