Blank black page instead of PDF document in Apple Safari web browser
Sometimes expectations are not justified. A person is looking forward to reading the user manual for the equipment he plans to buy, but instead ... a blank page appears on the screen. Indeed, sometimes a hyperlink does not lead to the next web page, but opens a PDF document directly in the browser. In most cases, this is not a problem, and everything looks so transparent to the user that he may not even think about what type of file is currently open. Modern browsers, without any third-party software add-ons, do an excellent job of opening PDF files that users usually view on mobile devices. But sometimes browsers safari, Google Chrome
and Firefox in MacOS X behave differently than the user expects. Instead of a linked PDF file, the frustrated and frustrated reader finds himself on a black or white page that carries absolutely no information. Fortunately, this problem has a simple solution, which we will consider today.
Difficulties with opening PDF-documents, users experienced back in June last year. The problem has already been addressed by such leading English-speaking messengers of the "apple" community as TidBITS and Mac OS X Hints. And yet this topic comes up again and again. For most users, everything opens as it should. But the essence of any problem is that, when it arose, a person is of little interest in how things are with the majority. He would like to do a good job. Since PDF documents on the Internet often provide instructions for household appliances and statistical information, the ability to open them without problems is extremely important for many users.
Just in case, let's clarify: we are talking about the version of Safari for Mac computers, and not about mobile version this famous Apple browser, which accounts for mobile Internet activity. In the market for web navigation for computer platforms, Safari occupies a decent, but much more modest position. On the reasons for this state of affairs, we
In most cases, the problem of reading PDF documents is rooted in two plug-ins from Adobe, which can "not find common language" With modern browsers. These are the additions: AdobePDFViewer.plugin and AdobePDFViewerNPAPI.plugin. They were installed with Adobe Reader and Adobe Acrobat Pro and were designed to allow browsers to open PDF documents developed by Adobe.
These plug-ins for versions of Adobe Reader or Adobe Acrobat Pro earlier than 10.1.3 are not currently compatible with some browsers. We are talking mainly about Safari 5.1 (or more later version), as well as the latest versions of Firefox. The only difference in the manifestation of the problem is that Safari will show the user a black page, and Firefox a white one. But in both cases, the page will be empty. If a user encounters a similar situation, this is a sure sign that Adobe plugins are installed on their system that are incompatible with this browser. But, of course, there is always a small chance of some other reason for this behavior of the browser.
Before proceeding with the removal of plug-ins that interfere with normal operation, be sure to close the browser. These extensions are located in the folder plug-ins, which in turn is located in the folder Library. This is not about a hidden library in your home directory, whose address is denoted as ~/Library/Internet Plug-Ins
No, in this case we are talking about a library that is accessed directly from the root directory of your hard drive, that is /Library/Internet Plug-Ins
Open this folder and find all files whose names begin with AdobePDFViewer and move them out of this folder (for example, temporarily "drag" them to the desktop). This is just a precaution so that the plugins can be easily restored if desired by returning them to their places. Moving these files will require you to enter the computer's administrator username and password.
However, sometimes these plugins can end up in the library of your home (Home) directory. In operating rooms Mac systems OS X 10.7 Lion and 10.8 this folder is hidden. To access it through the Finder, press the Option key and select the go to library action (Library in the English version of Go). This library has an internet add-on folder Internet plug-ins.
Go into it. If there are plugins AdobePDFViewer, move them out of this folder. The action will require you to enter an administrator login and password. In fact, everything is the same as in the library of the entire computer level, only with some subtleties that we considered necessary to consider separately.
Once the plugins have been moved out of the library, restart the web browser with the problem. Try opening the PDF document from the link. If the matter was really in Adobe plugins, then it will open correctly software tools the browser itself.
Sourced from TidBITS.com
Internet Explorer 11 & 10 considered the best versions proprietary Microsoft browser; Internet Explorer. With Windows 8 and Windows 7, you can use IE 10 and IE 11. In both of these iterations, some users encountered an issue that when they try to download and open a PDF file, Internet Explorer won't open PDF files.
Sometimes IE just hangs when loading PDF files. For this issue; you can use Task Manager to end your session. There were cases when many times, the file is loaded, but partially. They may open just fine in other browsers, but not in IE.
So, how can this IE behavior be solved? Well, a simple thing that could fix it is to set the default PDF reader to " reader presented in Windows 10 / 8.1 , or any other third party PDF reader of your choice. This will solve the problem. But if it doesn't, you can try this registry fix to fix the issue:
PDF files won't open in Internet Explorer
1. Click Windows Key + R combination, type put Regedt32.exe in Run dialog box and press Enter to open the Registry Editor.
2. Navigate to the next location:
HKEY_CURRENT_USER Software Microsoft Internet Explorer Main
3. In the right pane of this location, find TabProcGrowth named DWORD . This DWORD is actually short for Tab Process Growth; which sets the rate at which IE spawns processes New tab. If you find a DWORD it should have Value as 0 . If you don't find it, create it manually using Click right click Mouse -> New -> DWORD Value. Now click on the same DWORD to change its Data Value:
4. Now set the Value Data from 0 to 1. Click OK. Putting the value data 1 ensures that all tabs for this process frames are executed in a single tabulation process for a given mandatory integrity level (MIC) level. Now you can close the Registry Editor and reboot to see the results.
Hope you find the fix helpful!
Good afternoon. I use Google browser Chrome has been almost since the official announcement, and I really like it. And now it has already happened that even Opera has already switched to the Chromium engine and is essentially the same Chrome, only with a slightly modified shell and “other” functions. I already wrote once about how in browsers. Today we will touch on a slightly different topic, namely: disabling the plug-in for viewing built into browsers. I can't really explain why this is, but I don't like the fact that .pdf files open in the browser. I prefer using Acrobat Reader or STDU Viewer. If for some reason the plugin stopped working for you, and you need it, thanks to this article you will learn how to turn it back on.
1. Google Chrome and all browsers based on the Chromium engine (CoolNovo, RockMelt, Rambler Nichrome, Yandex.Browser, [email protected]). May also work for Opera above version 15.
1) Open a browser and type in address bar following:
chrome://plugins/
We get to the plugins page:
Chrome PDF Viewer" and disable it. Depending on the browser, the item may be called differently, for example, in Yandex browser viewer is called Yandex PDF Viewer.
That's it, now .pdf files will be opened through the program installed on your computer.
2 Mozilla Firefox
1) Open the browser, click on the button Firefox top left → "Settings" → "Settings".
2) In the window that opens, go to the "Applications" tab. Enter in search Portable Document Format:
3) Choose Portable Document Format (PDF) and click on the triangle on the right in the right column, here we choose what we want to do with PDF files by selecting last paragraph (use another) can be set certain program to open files. I prefer to select "Save File" which will bring up a file download window and then work with the file as I see fit.
PDF files do not open in Internet Explorer with Adobe Reader 10.0 - Users get a blank gray screen. How can I fix this for my users? (7)
There is a known issue opening PDF in Internet Explorer (v 6, 7, 8, 9) with Adobe Reader X (version 10.0.*). The browser window loads with a blank gray screen (and doesn't even have a Reader toolbar). It works great with Firefox, Chrome or with Adobe Reader 10.1. *.
I have found several workarounds. For example, clicking "Update" will load the document correctly. Update to Adobe Reader 10.1. *, or downgrading to 9. *, also fixes the problem.
However, all these solutions require from the user understand it. Most of my users get very embarrassed when they see this gray screen and end up blaming the PDF file and blaming the website for violating it. To be honest, until I researched this question, I blamed the PDF too!
So I'm trying to figure out a way to fix this issue for my users.
I considered providing a "Download PDF" link (which sets the Content-Disposition header to attachment instead of inline), but my company doesn't like that at all because we really want those PDF files to be displayed in the browser.
Has anyone else experienced this issue?
What are possible solutions or workarounds?
I really hope for a solution that perfect fits end users because I can't rely on them to know how to change their Adobe Reader settings or automatically install updates.
Here is the dreaded gray screen:
Change: Screenshot removed from file server! Regret!
The image was a browser, with a normal toolbar but solid gray background, no interface.
background information :
While I don't think the following information is related to my issue, I'll include it for reference:
This is an ASP.NET MVC application and jQuery is available.
The link to the PDF file has target=_blank so that it opens in a new window.
The PDF is generated on the fly and all content headers are set accordingly. The URL does NOT include the .pdf extension, but we set the content-disposition header with a valid .pdf filename and an inline parameter.
Change: Here source, which I use to work with PDF files.
First, the controller action:
Public ActionResult ComplianceCertificate(int id)( byte pdfBytes = ComplianceBusiness.GetCertificate(id); return new PdfResult(pdfBytes, false, "Compliance Certificate (0).pdf", id); )
And here is PdfResult (PdfResult , inherits from System.Web.Mvc.FileContentResult):
Using System.Net.Mime; using System.Web.Mvc; ///
In my case, the solution was quite simple. I added this header and the browsers opened the file in every test. header("Content-Disposition: attachment; filename="filename.pdf"");
We got this issue even after updating to the latest Adobe versions reader.
Two different methods solved this for us:
- Usage free version applications Foxit Reader instead of Adobe Reader
- But, since most of our clients use Adobe Reader, so instead of requiring users to use Foxit Reader, we started using window.open(url) to open the pdf instead of window.location.href = url . Adobe was losing the file handle in different iframes for some reason when the PDF was opened using the window.location.href method.
I had this problem. Reinstallation latest version Adobe Reader did nothing. Adobe Reader worked in Chrome but not in IE. This worked for me...
1) Go to IE Tools menu -> Compatibility View.
2) Enter the website with the PDF you want to view. Click OK.
3) Restart IE 4) Go to the website you entered and select PDF. He should appear.
5) Return to Compatibility View and delete the entered entry.
6) Adobe Reader is now working in IE on all websites.
This is a weird fix, but it worked for me. I had to go through the Adobe acceptance screen after reinstalling, which only appeared after I did the Compatibility View trick. Once adopted, it seemed to work everywhere. Pretty flaky material. Hope this helps someone.
I don't have an exact solution, but I'll share my experience with this in case they help anyone else.
From my testing, the gray screen only starts on slower machines. To date, I have not been able to recreate it on newer hardware. All my tests were in IE8 with Adobe Reader 10.1.2. For my tests, I disabled SSL and removed any headers that would disable caching.
To recreate the gray screen, I followed these steps:
1) Go to the page that links to the PDF file
2) Open the PDF in a new window or tab (or via context menu, or in target = "_blank")
3) In my tests, this PDF will open without error (however, I have received user reports indicating failure on first PDF load)
4) Close the newly opened window or tab
5) Open the PDF (again) in a new window or tab
6) This PDF does not open, but instead only the "gray screen" mentioned by the first user is shown (all subsequent PDFs that are loaded are also not shown until all browser windows are closed)
I have done the above test with several different PDFs (both static and dynamic) created from different sources and the gray screen issue always occurs when the above steps are done (on a "slow" computer).
To mitigate the problem in my application, I "torn" the page that links to the PDF (deleted piece by piece until the gray screen no longer occurred). In my particular application (built on a closure library), removing all references to goog.userAgent.adobeReader seemed to fix the problem. This exact solution won't work with jquery or .net MVC, but maybe this process can help you isolate the source of the problem. I haven't yet taken the time to isolate the part of goog.userAgent.adobeReader that triggers the error in Adobe Reader, but most likely jquery might have the same plugin detection code used in the closing library.
The machine is experiencing a gray screen:
Windows Server 03 SP3
AMD Sempron 2400+ at 1.6 GHz
256 MB memory
The machine does not experience a gray screen:
Windows XP x64 SP2
AMD Athlon II X4 620 at 2.6 GHz
4 GB memory
Experimenting more, the root cause in my application (calling goog.userAgent.adobeReader) was to access Adobe Reader via an ActiveXObject on a page with a PDF link. This minimal test case causes a gray screen for me (however deleting the ActiveXObject does not cause a gray screen).
I'm very interested if others can reproduce the problem with this test case and following the steps from my other post ("I don't have an exact solution...") on a "slow" computer.
Sorry for posting a new answer, but I couldn't figure out how to add a block of code to a comment on my previous post.
An example video of this minimal test case is below: http://youtu.be/IgEcxzM6Kck
I realize this is a rather late post, but still Possible Solution for the OP. I'm using IE9 on Win 7 and have been running into Adobe Reader gray screen issues for months trying to open an online PDF bank and credit cards. I could open everything in Firefox or Opera, but not in IE. I finally tried PDF-Viewer, set it as the default PDF viewer in my preferences and more problems. I'm sure there are other free viewers like Foxit, PDF-Xchange etc which will give top scores than Reader with fewer headaches. Adobe is like some of the other big companies that develop software to take it or leave it based... so I left it.
For Win7 Acrobat Pro X
Since I did all of this without double-checking to see if there was a problem after that, I'm not sure if they actually fixed the problem because of this, but one of them did. In fact, after doing #3 and rebooting, it worked great.
FYI: Below is the order in which I went through the repairs.
Go to Control Panel > Folder Options in each Control Panel General , View and Search click Restore Defaults button Reset Folders button
Go to Internet Explorer , Tools > Options > Advanced > Reset (I didn't have to remove personal settings)
Open Acrobat Pro X, under Edit > Preferences > General .
At the bottom of the page, select Default PDF Handler . I chose Adobe Pro X and click Apply .
You may be asked to reboot (I did).
Best wishes