Open
Bug 1479721
Opened 6 years ago
Updated 2 years ago
Saving a pdf page to pocket while in presentation mode breaks the "Page actions" and "Save to pocket" buttons
Categories
(Firefox :: Toolbars and Customization, defect, P3)
Firefox
Toolbars and Customization
Tracking
()
ASSIGNED
People
(Reporter: emilghitta, Assigned: adw)
References
Details
(Keywords: regression)
Attachments
(1 file)
7.28 MB,
image/gif
|
Details |
[Affected versions]: 63.0a1 (BuildId:20180730221422) 62.0b13 (BuildId:20180730180407) 61.0.1 (BuildId:20180704003137) 60.1.0esr (BuildId:20180621121604) [Affected platforms]: Windows 7 64bit. macOS 10.10. Ubuntu 16.04 32bit. [Steps to reproduce]: 1. Launch Firefox. 2. Access the following link:https://cdn4.libris.ro/userdocspdf/589/faust.pdf. 3. Switch to Presentation Mode. 4. Right click and select the "Save Page to Pocket" option. 5. Click on the "Page actions" and "Save to Pocket" buttons. [Expected result]: The "Page actions" and "Save to pocket" buttons are functional. [Actual result]: The buttons are not functional and the following error gets fired in the Browser Console each time the "Page actions" button is pressed: "TypeError: panelNode.anchorNode is null" [Regression range]: This seems to be a regression: Last good revision: 7f19b2c7adc598f40bf32808324bcba463cce627 First bad revision: 9f83f552a6118f1061ee5afd87578d9b5b82b308 Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=7f19b2c7adc598f40bf32808324bcba463cce627&tochange=9f83f552a6118f1061ee5afd87578d9b5b82b308 [Note] A workaround for this is to restart Firefox or to open a New Browser Window. For further information regarding this issue please observe the attached screencast.
Reporter | ||
Comment 1•6 years ago
|
||
Hi Drew, It seems that mozregression pointed out Bug 1395387 for causing this regression. Can you please have a look? Thanks!
Flags: needinfo?(adw)
Assignee | ||
Updated•6 years ago
|
Component: PDF Viewer → Toolbars and Customization
Flags: needinfo?(adw)
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → adw
Status: NEW → ASSIGNED
Priority: -- → P3
Updated•6 years ago
|
Comment 2•6 years ago
|
||
Too late for 63 but we could still potentially take a fix in 64/65.
Comment 3•6 years ago
|
||
Marking fix-optional for 64. We could still take a patch for 65, and if it's verified and doesn't seem risky, could still take fixes for 64 as well.
Comment 4•5 years ago
|
||
Reproduced on latest Nightly 68.0a1 (2019-03-31) (64-bit) on Ubuntu 16.04 x64
status-firefox68:
--- → affected
Updated•5 years ago
|
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•