Closed
Bug 836732
Opened 11 years ago
Closed 2 years ago
Buttons in pdf.js remain in hover state after selection
Categories
(Firefox :: PDF Viewer, defect, P1)
Firefox
PDF Viewer
Tracking
()
RESOLVED
FIXED
People
(Reporter: virgil.dicu, Assigned: calixte)
References
Details
(Whiteboard: [pdfjs-ux])
Attachments
(3 files)
Mozilla/5.0 (X11; Linux i686; rv:21.0) Gecko/20130131 Firefox/21.0 1. Have pdf.js enabled 2. Load http://www.stluciadance.com/prospectus_file/sample.pdf 3. Select Print 4. Select Cancel in the Print dialog Actual result: Print button remains in hover state until next click within the page. Happens with all buttons.
Reporter | ||
Comment 1•11 years ago
|
||
Not a regression, happens with F16 as well if I enable pdf.js. Didn't find any similar reports in bugzilla.
Reporter | ||
Comment 2•11 years ago
|
||
Changing to minor issue. Occurs across branches: Beta, Aurora, Nightly.
Severity: normal → minor
Version: 19 Branch → Trunk
Updated•11 years ago
|
Priority: -- → P3
Whiteboard: [pdfjs-c-ux]
Hi there! I am a University of Toronto compsci student interested in picking this bug up as my first Mozilla bug. Can I claim this? Also, I would love if anyone can mentor me on this!
This issue seems to be caused by the affected buttons using :focus
in addition to :hover
so that buttons appear hovered when tabbed to. Changing :focus
to :focus-active
for buttons and listboxes seem to fix this for me. I won't pretend I understand all of the CSS, though.
confirming with Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:97.0) Gecko/20100101 Firefox/97.0 BUILD: 20211226092042
Updated•2 years ago
|
Whiteboard: [pdfjs-c-ux] → [pdfjs-ux]
Assignee | ||
Updated•2 years ago
|
Assignee: nobody → cdenizet
Status: NEW → ASSIGNED
Comment 6•2 years ago
|
||
Comment 7•2 years ago
|
||
Commit merged into master by GitHub Authored by Jonas Jenwald (Snuffleupagus)
Updated•2 years ago
|
Severity: minor → S4
Has STR: --- → yes
Priority: P3 → P1
Updated•2 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•