Live data from Hacker News

Firefox introduces PDF viewer

blog.mozilla.org

161–170 of 200 posts

Re: Firefox introduces PDF viewer

#163
post #72

Earlier quoted context omitted.

... from there comes most infections on windows PCs running chrome.

This is ridiculous. The foxit plugin is fully sandboxed and I have not seen any exploits via any of the netsec lists I subscribe to.

With a couple Google queries, you can find out that the Chrome PDF viewer has had multiple vulnerabilities that allow code to be executed in the sandboxed environment, and that there have also been Chrome vulnerabilities that allow sandboxed code to escape the sandbox.

Sandboxing is certainly a good thing, but it's not perfect. Sandboxed code still increases the attack surface. The rationale behind pdf.js is that, because it's almost entirely unprivileged JavaScript, it's unlikely that there's a way to exploit a browser in the presence of pdf.js that wouldn't work in the absence of pdf.js.

Re: Firefox introduces PDF viewer

#164
post #143

Earlier quoted context omitted.

Mozilla has been saying for years that they will use the best engine, and take that engine's money if it's available. If Bing were clearly better than Google, they'd switch and be taking Microsoft's money.

They have said that during the time they are being offered the most money by the best search engine. That's easy. But Google keeps paying more which means Mozilla is after the highest bidder.

That is not how Mozilla's decision making works. There's considerably more to it than such simple economics.

As a non-profit, we are here to create a public good. It's actually goods, plural, and services too. Firefox and other Mozilla products and services exist to promote the Mozilla mission, not to enrich the Mozilla organization.

Yes. Sustainability is certainly a factor in some of our decision making. Mozilla would be foolish to ignore significant opportunities to increase its mission impact. But revenue for sustainability is not the sole or even the dominant factor in any major product decision at Mozilla.

Re: Firefox introduces PDF viewer

#165

Earlier quoted context omitted.

Google's PDF viewer refuses to save PDFs opened via the websites of some scientific journals. I'm not willing to play the proxy game every time I want to read journal papers so I save them locally. I stopped using Google's PDF viewer because of this misfeature.

Can you provide a citation or an example link for me to test? My understanding is that Chrome has the foxit plugin in a fully sandboxed environment. The PDF format nor the foxit system has any kind of DRM and shouldn't support this behavior.

There isn't any DRM, the plugin is just listening to a "suggestion" that it not let me save (no error, it just doesn't do anything when I click the save icon). Everything on ScienceDirect has this property. I just tested with this paper from my RSS feed (Chromium 24.0.1312.70).

http://www.sciencedirect.com/science/article/pii/S0045782513...

Re: Firefox introduces PDF viewer

#166
post #146

Earlier quoted context omitted.

I had dedicated PDF plugin installed [1]. They had no reason to switch to Firefox-native PDF rendering as the default for PDFs before getting some maturity to it. The very first PDF I encountered [2] won't render fine in it though it does very well in the dedicated PDF application [1]. [1] http://www.certifiedmastertech.com/1410/mechanicssecretspdf1... [2] http://www.tracker-software.com/product/pdf-xchange-viewer

What rendering problem do you see with the "mechanics' secrets" PDF? AFAICT, it looks fine with Firefox 22 on OSX. What OS and Firefox version are you using?

[deleted]

Re: Firefox introduces PDF viewer

#167

Earlier quoted context omitted.

Can you provide a citation or an example link for me to test? My understanding is that Chrome has the foxit plugin in a fully sandboxed environment. The PDF format nor the foxit system has any kind of DRM and shouldn't support this behavior.

There isn't any DRM, the plugin is just listening to a "suggestion" that it not let me save (no error, it just doesn't do anything when I click the save icon). Everything on ScienceDirect has this property. I just tested with this paper from my RSS feed (Chromium 24.0.1312.70). http://www.sciencedirect.com/science/article/pii/S0045782513...

I'm using Chrome not Chromium, and there's no save icon. Are you sure you aren't viewing this in a proprietary viewer? Typically you should be able to right click and get a save as option.

Re: Firefox introduces PDF viewer

#168
post #159

Earlier quoted context omitted.

I've been using Foxit reader for years without knowing that it was Chinese. Its a great product - fast as hell - beats the pants off Adobe.

I'd started using Foxit for the same reason. But the speed advantage is no longer an issue. Adobe had closed the gap and Acrobat reader now loads just as fast as Foxit. Besides, Acrobat's rendering is far superior to Foxit's (not to mention Foxit fails to load some PDF document or displays garbage) Acrobat is the new Foxit nowadays!

My problem with Adobe is that whenever I install any of their products I get the feeling I've just made my system more vulnerable to malware and the like. They've got an atrocious record when it comes to security bugs.

E.g. look at the size of this page: https://www.adobe.com/support/security/

Re: Firefox introduces PDF viewer

#169
post #146

Earlier quoted context omitted.

I had dedicated PDF plugin installed [1]. They had no reason to switch to Firefox-native PDF rendering as the default for PDFs before getting some maturity to it. The very first PDF I encountered [2] won't render fine in it though it does very well in the dedicated PDF application [1]. [1] http://www.certifiedmastertech.com/1410/mechanicssecretspdf1... [2] http://www.tracker-software.com/product/pdf-xchange-viewer

What rendering problem do you see with the "mechanics' secrets" PDF? AFAICT, it looks fine with Firefox 22 on OSX. What OS and Firefox version are you using?

Latest version of Firefox (32 bit) on Windows 7 x64 (fully updated).

The PDF shows up as blank other than the image on the very first page.

I figured. I use the following color settings in Firefox.

- Use system colors (checked) - Allow pages to choose their own colors, instead of my selections above (unchecked)

The problem goes away if the last item is checked.

Firefox by itself, nearly all websites, as well as my native PDF application, all work right with these and such settings. Firefox's new PDF functionality does not.

In any case, I reiterate my point. It was not a good decision to add this functionality to Firefox and right away switch the defaults.

Re: Firefox introduces PDF viewer

#170

Earlier quoted context omitted.

There isn't any DRM, the plugin is just listening to a "suggestion" that it not let me save (no error, it just doesn't do anything when I click the save icon). Everything on ScienceDirect has this property. I just tested with this paper from my RSS feed (Chromium 24.0.1312.70). http://www.sciencedirect.com/science/article/pii/S0045782513...

I'm using Chrome not Chromium, and there's no save icon. Are you sure you aren't viewing this in a proprietary viewer? Typically you should be able to right click and get a save as option.

I just confirmed that the same occurs with Chrome 24.0.1312.52 (Official Build 175374). I'm quite sure that I am viewing it in a proprietary viewer. Specifically, the Chrome PDF Viewer. Surely you've seen these buttons before?

http://i.imgur.com/80dO12V.png

In both Chrome and Chromium, clicking save here does nothing and "Save As" is greyed out in the right-click context menu. "Print" works in Chrome (though it takes time to produce a preview before I can print to PDF), but locks up Chromium.

This anti-user bullshit is usually less prevalent in non-proprietary software.

Post reply on HN