Closed
Bug 686286
Opened 13 years ago
Closed 5 years ago
Downloading without enough space does not trigger a proper message
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: csuciu, Unassigned)
Details
Attachments
(3 files)
Mozilla/5.0 (Android;Linux armv7l;rv:9.0a1)Gecko/20110911 Firefox/9.0a1 Fennec/9.0a1 Device: HTC Desire OS: Android 2.2 Steps: 1. Install nightly 2. Make sure that there is not much space available on device 3. Go to http://www.thinkbroadband.com/download.html and start downloading a file larger than the available space on device. 4. Wait till memory is full. Expected: The device should say that "there's not enough space" when memory is full Actual: A message box without any content is displayed. Sometimes this message box is improperly positioned at the bottom of the screen. Also when changing orientation to landscape the message box disappears. Please see the attached screenshot.
Comment 1•13 years ago
|
||
Does this happen on a Gingerbread device? What do the logs say when you get that empty dialog?
Reporter | ||
Comment 2•13 years ago
|
||
I tested this on Samsung Nexus S with Android 2.3. The same empty dialog is displayed in foreground when memory is full, but this time, the correct dialog can be seen in the background. Because the OK button from the empty dialog is unresponsive, the correct dialog cannot be brought to foreground. Fennec must be restarted in order to dismiss the empty dialog. Please see the attached screenshot.
Reporter | ||
Comment 3•13 years ago
|
||
Reporter | ||
Comment 4•13 years ago
|
||
Comment 5•13 years ago
|
||
Wes - Does this seem like the double-dialog problem your dialog patch fixes?
Updated•13 years ago
|
Summary: Running out of memory does not trigger a proper message → Downloading without enough space does not trigger a proper message
Comment 6•5 years ago
|
||
Closing all opened bug in a graveyard component
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•