Closed
Bug 1392207
Opened 9 years ago
Closed 8 years ago
Firefox crashes when using cursor keys or quicklook in open file dialog on macOS
Categories
(Core :: Widget: Cocoa, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1361432
People
(Reporter: arglborps, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:55.0) Gecko/20100101 Firefox/55.0
Build ID: 20170814073321
Steps to reproduce:
This is a macOS specific bug. It is not particular to any version of macOS, though.
Go to any site with an upload button that spawns an open/select file dialog. Click the button, select a file with a mouse click, then use the cursor keys to select another file, alternatively when a file is selected, press space to invoke Quick Look.
Actual results:
Instead of shifiting the selection to the next file or opening a QuickLook window, Firefox will crash instantly.
Expected results:
Firefox should either move the selection highlight to the next selected file or with QuickLook simply display the QuickLook window on top of all other windows (as any other browser does in this case)
Comment 1•9 years ago
|
||
Please provide the crash ID from the page "about:crashes".
https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report explains how to do this.
When doing so, please also add the keyword "crashreportid" to the "Keywords" field of this report.
Flags: needinfo?(arglborps)
| Reporter | ||
Comment 3•9 years ago
|
||
The way it crashes is atypical, it's entirely silent, there's no crash dialog from the OS nor Firefox itself, the app is just gone immediately. In some cases actually the firefox background process just keeps running and goes haywire on CPU load after the crash. when I visit about:crashes I get an empty page saying "No crash reports have been submitted."
Flags: needinfo?(arglborps)
Updated•9 years ago
|
Component: Untriaged → Widget: Cocoa
Product: Firefox → Core
Updated•8 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•