Closed
Bug 981783
Opened 11 years ago
Closed 11 years ago
New progress bar doesn't go away sometimes
Categories
(Firefox for Android Graveyard :: Theme and Visual Design, defect)
Tracking
(fennec30+)
RESOLVED
WORKSFORME
| Tracking | Status | |
|---|---|---|
| fennec | 30+ | --- |
People
(Reporter: kats, Unassigned)
References
Details
Attachments
(2 files, 1 obsolete file)
When I start Firefox on a Galaxy Tab 10.1 running Honeycomb in landscape mode I see the new progress bar thingy come up and it never finishes. If I load a page a *second* progress bar comes up on top of it and behaves normally. However the first one never really goes away, and even if I slide the URL bar off the screen it remains in place. See screenshot.
| Reporter | ||
Updated•11 years ago
|
Version: unspecified → Firefox 30
| Reporter | ||
Updated•11 years ago
|
Component: General → Theme and Visual Design
Comment 1•11 years ago
|
||
This partly sounds like bug 980853 which should have been fixed via bug 980438 on a build from the 8th onwards.
| Reporter | ||
Comment 2•11 years ago
|
||
I saw this on today's nightly as well as a local build from recent m-c.
Comment 3•11 years ago
|
||
Yes we saw this earlier. Seemed like bug 980853. Though this is reproducible on today's trunk on a Android 3.0 tablet for me as well.
Updated•11 years ago
|
tracking-fennec: --- → ?
Comment 4•11 years ago
|
||
I'm able to reproduce this issue on Motorola RAZR with Android 4.0.4
Comment 5•11 years ago
|
||
Attachment #8390382 -
Attachment is obsolete: true
Comment 6•11 years ago
|
||
I wonder if this is related to the also recently filed bug 982896
Comment 7•11 years ago
|
||
Does this affect Nightly *and* Aurora?
Comment 8•11 years ago
|
||
Can we retest in tomorrow's Nightly? Could be fixed by bug 981676?
tracking-fennec: ? → 30+
Comment 9•11 years ago
|
||
Fixed with the progress bar backouts.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Updated•5 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•