חיפוש בתמיכה

יש להימנע מהונאות תמיכה. לעולם לא נבקש ממך להתקשר או לשלוח הודעת טקסט למספר טלפון או לשתף מידע אישי. נא לדווח על כל פעילות חשודה באמצעות באפשרות ״דיווח על שימוש לרעה״.

מידע נוסף

Preview in Firefox for PDF stopped working with FF 73.0.1

  • 6 תגובות
  • 1 has this problem
  • 12 views
  • תגובה אחרונה מאת cor-el

more options

I updated to FF 73.0.1 a couple days ago and now when I navigate to a PDF file, it no longer will Preview in Firefox. Instead, it goes to the Save File option.

I've tried setting it in the Options/Applications and all the other choices work fine except the Preview in Firefox.

I updated to FF 73.0.1 a couple days ago and now when I navigate to a PDF file, it no longer will Preview in Firefox. Instead, it goes to the Save File option. I've tried setting it in the Options/Applications and all the other choices work fine except the Preview in Firefox.

כל התגובות (6)

more options

Is the builtin PDF Viewer still enabled if you check pdfjs prefs (pdfjs.disabled) on the about:config page ?

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.


See also:

more options

pdfjs.disabled is set to its default value of false. That's not it.

more options

I think I figured it out. The website's links to the pdf files were ftp. When I tried a website with https it worked as expected.

more options

How does the server send the PDF file if you check this in the Web Console (Requests and XHR) and Network Monitor ?

If the file is send a "application/pdf" then Firefox will open the file in a Firefox tab. If the file is send with another content type then Firefox will offer to save the file.

more options

I am unable to determine how the file is sent. Looking at the source, there's a <a> tag with the href="ftp://..." but also has target="_blank" so it's opening a new tab and then doing the save box. So there is no console view on the new tab.

I'm not going to worry about it any more.

more options

You can alternatively use the Browser Console and enable messages from content processes via the cogwheel button in the Console.