-
Notifications
You must be signed in to change notification settings - Fork 4.5k
File block: Use native feature detection for pdf support #63044
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
Conversation
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @asdofindia! In case you missed it, we'd love to have you join us in our Slack community. If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information. |
Test ReportDescription✅ This report validates whether the indicated patch works as expected. Patch tested: https://patch-diff.githubusercontent.com/raw/WordPress/gutenberg/pull/63044.diff Environment
Actual Results
Additional Notes
cc @Mamaduka Supplemental Artifacts |
I've force pushed the whitespace change for fixing lint. The unit tests seem to fail for reasons outside this PR. Do let me know if anything else needs to be done. |
Yes, it's an unrelated problem. This issue should be fixed once #71009 is merged, but will require another rebase. Update: Merge the fix. Rebasing will resolve the problem now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @asdofindia!
Fixes #58891
Relies on https://developer.mozilla.org/en-US/docs/Web/API/Navigator/pdfViewerEnabled
What?
This PR adds a reliable way to detect pdf viewer support.
Why?
It fixes #58891 and deterministically looks for pdf viewer support.
How?
We check whether the browser signals that pdf viewer is available and if so, immediately assumes that the browser supports pdf viewing (without relying on user agent detection). It falls back to the old behavior if this pdfViewerEnabled property is not available in navigator.
Testing Instructions
Testing Instructions for Keyboard
Same as above.