Open
Bug 988686
Opened 11 years ago
Updated 2 years ago
Display favicon from top left corner of large images and PDFs if no domain favicon is available
Categories
(Firefox :: PDF Viewer, defect, P3)
Tracking
()
NEW
People
(Reporter: jboriss, Unassigned)
References
Details
(Whiteboard: [pdfjs-ux] p=13)
Attachments
(1 file)
(deleted),
image/png
|
Details |
This is an engineering counterpart to bug 960940, which describes the user experience decision behind this behavior.
Currently, for images larger than pref browser.chrome.image_icons.max_size (hereafter MS) and for PDFs with no available domain favicon, no image is shown in Firefox tabs.
This is not useful to users and cannot distinguish one tab with an image or PDF from another. Instead, let's show in the tab an MS-sized rectangle out of the top left corner of PDFs and images larger than MS and show that as a preview on the tab.
Acceptance Criteria:
1. Favicon is shown on tabs with images and PDFs larger than pref browser.chrome.image_icons.max_size, which is cut from the top left corner of the image or PDF if no domain favicon is available
2. Stretch Goal: Cut image from top right if PDF is written in RTL language
Reporter | ||
Comment 1•11 years ago
|
||
Note: Bug 988687 covers preview of images smaller than pref browser.chrome.image_icons.max_size
Updated•11 years ago
|
Priority: P5 → P3
Whiteboard: [pdfjs-c-ux][pdfjs-f-good-beginner-bug]
Reporter | ||
Updated•11 years ago
|
Flags: firefox-backlog?
Updated•11 years ago
|
Flags: firefox-backlog? → firefox-backlog+
Updated•11 years ago
|
No longer blocks: fxdesktopbacklog
Whiteboard: [pdfjs-c-ux][pdfjs-f-good-beginner-bug] → [pdfjs-c-ux][pdfjs-f-good-beginner-bug] p=0
Comment 3•11 years ago
|
||
Removing beginner-bug status here, following the triage meeting.
Whiteboard: [pdfjs-c-ux][pdfjs-f-good-beginner-bug] p=0 → [pdfjs-c-ux] p=0
Updated•11 years ago
|
Whiteboard: [pdfjs-c-ux] p=0 → [pdfjs-c-ux] p=13
Updated•3 years ago
|
Whiteboard: [pdfjs-c-ux] p=13 → [pdfjs-ux] p=13
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•