I know that printing hasn't been hooked into the fxmetro yet, but when you tap on the "print" button while using PDF.js the entire browser will become very unstable. Navigation App Bar stops working and the browser becomes very sluggish and slow. Creating this as a placeholder to make sure that printing is also tested under PDF.js one it's added into fxmetro. Steps to reproduce the issue: 1) Open fxmetro 2) Go into about:config and switch pdfjs.disabled = false 3) Go into Google and search for "PDF" 4) Select a PDF from the search results (I usually select the Bitcoin document) 5) Once the PDF has loaded into PDF.js, tap on the "Print" icon. You'll notice that the Navigation App Bar will become very unstable and it will make the browser very hard to use. Current Behavior: - Selecting "Print" under PDF.js slows down fxmetro and makes it almost unusable Expected Behavior: - Taping on "Print" shouldn't cause that many issues, even if printing hasn't been added into fxmetro

Is Fx28 beta affected? If so, we need to track it for that release.

This doesn't seem to be affecting Fx28 BETA. You can enable PDF.js through about:config but it will just open the pdf file using default program that's set by Windows. Bug #967969 added the handlers and was only added into Nightly. (Checked on both X1 Carbon and the Surface Pro 2)

Mass close of bugs in obsolete product https://bugzilla.mozilla.org/show_bug.cgi?id=1350354