Closed
Bug 1112536
Opened 11 years ago
Closed 11 years ago
[Flame][Settings]The last item in Settings doesn't display.
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(b2g-v2.1 affected, b2g-v2.2 unaffected)
RESOLVED
WORKSFORME
| Tracking | Status | |
|---|---|---|
| b2g-v2.1 | --- | affected |
| b2g-v2.2 | --- | unaffected |
People
(Reporter: jihao, Unassigned)
Details
Attachments
(2 files)
[1.Description]:
[Flame][v2.1][Settings]In "Settings" view (including every sub-menu of settings),if items on the view take more than 1 page to display, the last item will not be displayed.
Attachment: logcat_flame_1405.txt and last_item.3gp
Occurrence time: 14:05
[2.Testing Steps]:
Set up: We don't connect network.
1. Tap E.me on home screen.
2. Type some character and "No internet connection" pops up.
3. Tap the gear button go to settings
4. Connect a wifi.
5. Back to E.me page and tap search button.
6. Tap Home button and tap Settings
7. Scroll down screen to the bottom.
[3.Expected Result]:
7. The last item should be displayed.
[4.Actual Result]:
7. The last item doesn't display in Settings.
[5.Reproduction build]:
Flame 2.1 build:
Gaia-Rev 79286eafe67707d1330966c1b1413b2d0de595d9
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/222a62b532db
Build-ID 20141216001202
Version 34.0
[6.Reproduction Frequency]:
Always Recurrence,5/5
TCID: Free Test
Note:1.This issue also exist on other page while the items take more than 1 page to display.
2.When reboot device,all item will be displayed correctly.
status-b2g-v2.2:
--- → unaffected
We can't reproduce this issue on latest Flame 2.1
Reproducing rate: 0/5
Flame 2.1 build:
Gaia-Rev af0131a6ba7bf12ac3dc4d94225a7f4e62589ecb
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/b6b59143a192
Build-ID 20150211001259
Version 34.0
Device-Name flame
FW-Release 4.4.2
FW-Incremental eng.cltbld.20150211.034325
FW-Date Wed Feb 11 03:43:36 EST 2015
Bootloader L1TC000118D0
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•