Closed Bug 974558 Opened 10 years ago Closed 10 years ago

[B2G][Notifications]Unable to scroll through notifications

Categories

(Firefox OS Graveyard :: Gaia::System, defect)

Product:
Firefox OS Graveyard
Component:
Gaia::System
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(blocking-b2g:1.4+, b2g-v1.3 unaffected, b2g-v1.4 affected)

Status:
RESOLVED WORKSFORME
Milestone:
1.4 S2 (28feb)
Project Flags:
blocking-b2g 1.4+
Tracking Flags:
Tracking Status
b2g-v1.3 --- unaffected
b2g-v1.4 --- affected

People

(Reporter: astole, Assigned: mikehenrty)

References

(
URL
)

Details

(Keywords: regression, Whiteboard: [systemsfe][p=1]) 

The user is unable to scroll through notifications when there is more than five notifications.

Repro Steps:
1) Updated Buri to BuildID: 20140219040204
2) Receive more than five notifications
3) Open Notifications menu
4) Attempt to scroll

Actual:
User is unable to scroll through the notifications.

Expected:
User can scroll to different notifications

Environmental Variables:
Device: Buri v1.4 M/C Mozilla RIL
BuildID: 20140219040204
Gaia: ac06cfbd2baf6494ffbb668cc599e3892cd5e17b
Gecko: bf0e76f2a7d4
Version: 30.0a1
Firmware Version: V1.2-device.cfg

Repro frequency: 100%
See attached: Video
Attaching URL to video
URL: http://youtu.be/uYF6sVvuPaw
Can we check what happens on 1.3?
Keywords: qawanted
The user is able to scroll through the different notifications in the latest 1.3.

Environmental Variables:
Device: Buri v1.3 Mozilla RIL
BuildID: 20140219004003
Gaia: a43904d9646109b48836d62f7aa51e499fbf4b2e
Gecko: 97922b6daad1
Version: 28.0
Firmware Version: V1.2-device.cfg
status-b2g-v1.3: --- → unaffected
status-b2g-v1.4: --- → affected
Keywords: qawanted → regression, regressionwindow-wanted
blocking-b2g: --- → 1.4?
QA Contact: sarsenyev
blocking-b2g: 1.4? → 1.4+
Whiteboard: [systemsfe]
Mike, can you take a look here?
Assignee: nobody → mhenretty
Target Milestone: --- → 1.4 S2 (28feb)
This issue started reproducing on the 02/15/14 1.4 build.

The following regression window was found using tinderbox builds:

- Works -
Device: Buri v1.4 MOZ RIL
BuildID: 20140215095648
Gaia: 8ac5dc6b76709e742cb923c58d1f4b415b3e08fb
Gecko: 9394396013a8
Version: 30.0a1
Firmware Version: V1.2-device.cfg

- Broken -
Device: Buri v1.4 MOZ RIL
BuildID: 20140215100248
Gaia: f75b9dac351c0676f0fc696fa36330933985ed36
Gecko: 4ebfb26de52c
Version: 30.0a1
Firmware Version: V1.2-device.cfg


Additionally, after swapping the builds' geckos, I've found that this is a gaia issue.

last working gaia/first broken gecko = no repro
first broken gaia/last working gecko = repro
Keywords: regressionwindow-wanted
QA Contact: sarsenyev → mvaughan
I am no longer able to repro, and after doing a bisect I think this issue was fixed with bug 975018:
https://github.com/mozilla-b2g/gaia/commit/155560b40d94c4ef94801835437e63f06f5d15c5

The initial regression appears to be caused by bug 971006, which was reopened after the backout.

Matthew, can you verify that this is not happening on master anymore?
Keywords: qawanted
This issue no longer reproduces for me. I tested this on the 02/26/14 1.4 build on a Buri.

Device: Buri v1.4 MOZ RIL
BuildID: 20140226040201
Gaia: 80d6405725788327102cab36e8d8c017cf25fb23
Gecko: 626d99c084cb
Version: 30.0a1
Firmware Version: V1.2-device.cfg
Keywords: qawanted
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Whiteboard: [systemsfe] → [systemsfe][p=1]
You need to log in before you can comment on or make changes to this bug.