Apr 28 2020 12:35 PM
Apr 28 2020 12:35 PM
When I click on a pdf file either in search results or the document library web part the file opens in the web browser. When I put a link to the same file in an image web part the file opens in the SharePoint pdf viewer.
Is there a way to change the default or disable the SharePoint pdf viewer so that clicking on a link to a pdf will always open in the web browser?
It normally wouldn't make a difference but there appears to be a bug in the SharePoint pdf viewer that doesn't recognize all hyperlinks. They show in blue but there is no link. We have a pdf with many hyperlinks to other documents on the SharePoint site. When the pdf is opened in a web browser all the hyperlinks work correctly.
If anyone is curious how to make the hyperlinks fail in the SharePoint viewer here is what we did. We created a Word document and set the hyperlink base to be a SharePoint Document Library. In the document there are various hyperlinks - some to external sites and some to filenames in the Document Library. The Word document was saved as a pdf. The pdf was opened in Adobe reader and all the links - both external and SharePoint worked. We uploaded the pdf to SharePoint. If the file is opened in the web browser all hyperlinks work. If it is opened using the SharePoint pdf viewer only the external links work. The links to files in the Document Library don't.
If we could just get rid of the SharePoint pdf viewer everything would work fine since everyone's web browsers can view pdf files.
Apr 29 2020 10:23 AM
For security reasons, SharePoint prefers to open PDF files, especially with a hyperlink through SharePoint PDF viewer. Syncing the Document Library and open the PDF file from the computer may resolve this.
I know it's bothering many users but SharePoint trying to keep the environment safe.
Hope this resolve the issue :)
Apr 29 2020 11:14 AM
No. That can't be true. Otherwise, they would not allow the Open in Browser option at all and it wouldn't be the normal behavior when clicking on a pdf from search results or from the Document Library Web Part.
Jul 30 2020 12:21 AM
Yes I have also found this very annoying...we have a system which is fronted by a Visio diagram on the home page...the links from the visio shapes open the pdf documents in full web browser mode.
Where as the quick links web part underneath only open the pdfs in the sharepoint web viewer and we don't want our users to see version history for a start (thats for the Quality control team only) but actually more importantly the sharepoint pdf viewer displays the full A4 page in the window, and its difficult to read whereas Id prefer the full browser view as it fits the page by width and you can actually read the content.
You would that that there being a different URL for standard open and the web browser open the link should work for each type of experience. It's baffling.
Oct 16 2020 05:45 AM
@Darren Graham This also has user experience implications: consider a Sharepoint communications site with links to various PDF documents. When you link to those documents using the Quick Links webpart and the site opens them using the SharePoint pdf viewer, the viewer puts its own toolbar up. One of the options on that toolbar is a "close" cross. Hitting that cross does not back you out to the page, rather it just closes the document and dumps you into the directory the PDF sits in, which the user may never even have seen before and certainly might not be familiar with.
This is very bad from a UX standpoint, and even just a URL modifier that I could manually append to each Quick Link to use the browser's own PDF viewer would be helpful.
Mar 09 2021 08:04 PM
Dec 14 2021 04:33 AM
Dec 15 2021 05:25 AM
We too are not happy with the lack of functionality. We have a PDF of a word document, which contains a table. When the pdf is opened in sharepoint, we are unable to search the table in the pdf! When you open in the browser, we can search the document, and hit the table. It is very frustrating that we have to open, then open in browser, to obtain search functionality.