Closed Bug 834223 Opened 11 years ago Closed 3 years ago

Add pref to disable the notification bar about the PDF file not being displayed correctly

Categories

(Firefox :: PDF Viewer, enhancement, P3)

enhancement

Tracking

()

RESOLVED INVALID

People

(Reporter: tamma00, Unassigned)

Details

(Whiteboard: [pdfjs-c-feature])

Currently the notification bar is show even on a slightest problem when displaying a PDF file in-browser (as described in bug 767455 comment #1). Even tho the user might not notice anything wrong with the displayed file. Thus i can become quite anooying when opening many PDF files a day. Secondary use of this pref would be to turn this on when viewing/dealing with known broken PDF files. So the user knows that the files are not displayed correctly but wants to disable the notification anyway.

The pref would look something like "pdfjs.AlwaysDisplayNotificationBar" with default value "true". Currently i can hide the bar with custom CSS rule but that disables all notification bars and for obvious reasons is not advisable.

Secondary solution would be to add extra button to the notification bar saying "This file displayed correctly" and when user clicks that then the bar dissapears and next time opening the same file the bar is no longer displayed. So essentially it rembembers the user feedback.
Priority: -- → P5
OS: Windows 7 → All
Priority: P5 → --
Hardware: x86_64 → All
Version: 19 Branch → unspecified
Priority: -- → P3
Whiteboard: [pdfjs-c-feature]
Status: UNCONFIRMED → NEW
Ever confirmed: true
To get the workaround to work you have to create a folder called chrome in the firefox profile folder, and inside that folder create a file called userChrome.css. Then add the following two lines to the new file. (If that file already exists just add the second line below.)

@namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul);
notification[value="pdfjs-fallback"] { display: none; }

We no longer show this bar.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.