Closed
Bug 851648
Opened 13 years ago
Closed 12 years ago
[B2G][Everything.me] Selecting an Everything.me folder loads a blank page
Categories
(Firefox OS Graveyard :: Gaia::Everything.me, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: ckreinbring, Unassigned)
Details
Attachments
(1 file)
|
273.87 KB,
image/png
|
Details |
Repro steps:
1. From the homescreen, swipe to the right to access everything.me
2. Select any of the folders.
3. Observe the page that loads.
Expected:
Links to sites that fit the theme of the folder appear.
Actual:
Unless there are phone apps that fit the theme, the page will not contain any links.
Note: After about 45 minutes, the site links started appearing again in the Everything.me folders.
Unagi build 20130314114915
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/8e9dd87b4f3b
Gaia: 69dbcd84085f10bec0c0189b926ffb535b14dcfe
Kernel Date: Dec 5
Updated•13 years ago
|
Component: General → Gaia::Everything.me
Comment 1•13 years ago
|
||
Our automation caught this too, in precisely the same way:
http://qa-selenium.mv.mozilla.com:8080/view/B2G/job/b2g.unagi.gaia.v1-train.ui/324/testReport/
Comment 2•13 years ago
|
||
(In reply to Stephen Donner [:stephend] from comment #1)
> Our automation caught this too, in precisely the same way:
>
> http://qa-selenium.mv.mozilla.com:8080/view/B2G/job/b2g.unagi.gaia.v1-train.
> ui/324/testReport/
And now, with a build from 2:53pm, where we do a make-reset gaia and pull in/build with the v1-train (http://qa-selenium.mv.mozilla.com:8080/view/B2G/job/b2g.unagi.gaia.v1-train.ui/325/testReport/), we're no longer seeing that issue in automation.
Comment 3•13 years ago
|
||
This issue was due to temporary server API downtime
| Reporter | ||
Comment 4•12 years ago
|
||
Haven't seen this happen since, so I'm resolving as Worksforme.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 5•12 years ago
|
||
Still haven't seen it happen again, so verifying as Worksforme.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•