You can set the pdfjs.disabled pref to true on the about:config page to disable the build-in PDF viewer and use the Adobe Reader instead.

See:

• https://support.mozilla.org/kb/view-pdf-files-firefox-without-downloading-them

Right, thanks for the Reply. But that does not address the issue really. Will the firefox PDF viewer support fillable fields, etc. in the future? Or is this a bug?

This is under development.

See:

• bug 739043 - Can't fill fillable PDF forms with PDF Viewer

(please do not comment in bug reports: https://bugzilla.mozilla.org/page.cgi?id=etiquette.html)

This new viewer was an ugly surprise. I DO NOT want pdfs to open in Firefox. I want FIrefox to give me the option to open or download. If I select open, I want it to open in my copy of Acrobat (not the Reader), and certainly not inside Firefox. Can anybody help me?

Additionally, there are a lot PDFs which do not show included images correctly when opened with the build-in viewer or can't display effects like shadows or gradients (for example: http://www.peginc.com/freebies/Rippers/RippersHeroes.pdf), some fonts aren't displayed right and accents (you know, umlaute and such things) are missing in many cases. Anti-aliasing for fonts isn't working either. Any chance to change that fast? Or deactivate the build-in viewer until it works properly?

Another issue with the built-in pdf viewer is the lack of a search function to look for words in the displayed pdf file. Maybe I overlooked something, but could not find a button for it.

hello drmarkweber, the normal search tools in firefox that work in websites will also work in the built-in pdf viewer: How to search the contents of the current page for text or links

nobler: you can use cor-el's method to disable the firefox's PDF viewer.

I am in the same boat as webphenom. We are in the business of fillable PDF forms. Is it possible to make the firefox's PDF viewer can load a filled pdf forms? Now I have this pop-up bar "This PDF document might not be displayed correctly ...." from PDF viewer when I load a filled pdf form.

The default pdf viewer in FF 19 is simply not fit for purpose. It displays/prints wrong typefaces with bad character spacing, sometimes displays pages as completely blank, prints some colours and not others, ... I could go on. It is easy to change back to having Foxit (or any other) as the default viewer, but I am concerned that other users of Firefox who do not know how to do that will see pdf files of mine very badly reproduced and naturally will think it is my fault. Please stop making the built-in pdf viewer the default until it works properly.

Beloved Firefox developers, please do as Kdiment says, disable the built-in PDF viewer until it works. We just have an eventful demonstration of our next BIG thing this morning (the pdf forms are not fillable, filled PDF forms display as unfilled pdf...), and our boss thinks we xxxx the bed. In addition, where is pdf.js? NoScript blocks this item (another item that our boss thinks it is our fault) when the built-in pdf viewer is enable.

I have found that all one needs to do is to go into tools/options/applications and change "Preview in Firefox" to "Use Adobe Acrobat (in Firefox") and you can easily change back to the previous mode.

I also actually love the Preview in Firefox, it allows you to open links in a Adobe document in a new tab and other sweet things.

I agree, the default setting should be a normal download for PDFs. After installing v19.0, I immediately ran into a website where a PDF wouldn't load within the browser, I discovered this default setting and changed the action to "Always ask" so that I could get a proper version of the PDF file.

hello, Axis

I understand the steps to rollback to the previous mode. Can you imagine 100s users calling our tech support line and asking why our app does not work suddenly? Having said that, may be this is our fault that we do not read the release notes carefully. Anyway, I need to find a way to read Firefox's pdf option in via JavaScript.

TL

Rather than be repetitive my comments in a similar thread are here (about half way down the sreen):

https://support.mozilla.org/en-US/questions/950939

• /questions/950939#answer-410247 _{edit, direct link added -J99}

Regards, Axis

I agree, this was indeed an ugly surprise! Default behavior should never automatically change; any new features should only be enabled by consenting, deliberate opt-in. In my case, Acrobat suddenly stopped working after Firefox did an automatic update, and I had to search for this answer in the middle of an urgent project before I could continue working.

Good point richpasco
but you would do better adding such a comment to feedback. developers may review digests of feedback information, but will not see comments in this forum.

• http://input.mozilla.org/en-US/feedback

john99, can you be more specific on where to add my comment: where is this "feedback" you mention, and how does one access it?

It is available by default as an icon or option top right on your Firefox toolbar, or by clicking/double clicking the blue link

• http://input.mozilla.org/en-US/feedback <--- clickable link

Theoretically you could file a bug yourself for such a request, but it would have little chance of success, unless you are able to get support and interest for the idea in advance.

There may be developer's forums or mailing lists where you may be able to discuss this matter, but I would not know which ones may be applicable.

• listing http://www.mozilla.org/about/forums/#general-development

We use embedded JavaScript in our PDFs enabling the customer to automatically print the PDF when it is opened.

It works in every other browser. It does not work in FF19 with pdfjs.

We're getting grief from our customers over this unannounced introduction.

Please explain this behaviour which is not consistent with other web browsers. I thought that was the job of IE???

Sorry TicketSource,
The purpose of this forum is answering simple support questions involving a user fix to Firefox.

We do not deal with requests for enhancement to Firefox software, or explaining the mysterious decisions made by developers. You will need to look elsewhere for an answer to that, as explained in my last post.

I realise this is not the answer you hoped for but not much I can do to help.