Closed
Bug 763107
Opened 12 years ago
Closed 11 years ago
Android Website Testing page stops updating after testing for a while
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(firefox25 ?)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox25 | --- | ? |
People
(Reporter: mcsmurf, Unassigned)
References
()
Details
To reproduce: 0. Fetch current mozilla-central Fennec build 1. Go to http://mobile.aaronmt.com/topsites/_design/topsites/index.html 2. Tap on the link to the page that should be tested, link will open in new tab 3. Tap a bit around on that page, tap on back button until you get back to the original tab with the Android Website Testing page 4. Tap on "Skip Site" button. Ideally you should now notice that the button does not turn yellow on tapping as it should be. Also the link does not update, normally a new link should appear. Unfortunately I cannot reproduce this bug with every page that appears on the Android Website Testing page, sometimes you have to tap around on two or three websites to reproduce this problem. I did my testing on a Galaxy S2 in landscape mode. When it stops rendering it helps to rotate the device to portrait mode, then it renders the new link.
Reporter | ||
Comment 1•12 years ago
|
||
For example I now had to "test" 10 websites to reproduce this bug. I'll try to find out if there's a better way to reproduce.
Comment 2•12 years ago
|
||
I was not able to reproduce this, but while testing, Fennec crashed several times. Accessing the crash it returned "Crash Not Found", one of the crashes was: https://crash-stats.mozilla.com/report/index/bp-73bd3a3c-cdde-4cb6-86f7-46f4c2120622. Frank, is this still reproducible for you?
Comment 3•12 years ago
|
||
(In reply to Andreea Pod from comment #2) > I was not able to reproduce this, but while testing, Fennec crashed several > times. Accessing the crash it returned "Crash Not Found", one of the crashes > was: > https://crash-stats.mozilla.com/report/index/bp-73bd3a3c-cdde-4cb6-86f7- > 46f4c2120622. > > Frank, is this still reproducible for you? I'm unable to reproduce either on a variety of devices. The crash you mentioned is bug 765463.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 4•12 years ago
|
||
Well, I still see this bug :) also see Bug 754684, I suspect it's related.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Updated•12 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•11 years ago
|
status-firefox25:
--- → ?
Reporter | ||
Comment 5•11 years ago
|
||
Just fyi: I've got a new Android mobile now since two weeks ago and I have not seen those website update bugs like this bug here or Bug 754684 happen on that device (Sony Xperia Z1). So I guess it might be somehow related to the hardware/software driver stack on the Galaxy S2.
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•3 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
•