Closed Bug 1170793 Opened 11 years ago Closed 11 years ago

[Aries] When using scroll wheel picker the screen underneath picker flashes on screen repeatedly

Categories

(Core :: Graphics, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1174810
Tracking Status
b2g-master --- affected

People

(Reporter: bzumwalt, Unassigned)

References

()

Details

(Whiteboard: [3.0-Daily-Testing],[spark],[gfx-noted])

Description: When user scrolls up or down on a wheel picker (e.g. choosing time or date in Calendar or Clock) the screen in background flickers repeatedly into view. Unable to reproduce after reproducing repeatedly over the course of writing bug. Adding steps-wanted. Repro Steps: 1) Update a Xperia Z3 Compact (B2G) to 20150602115822 2) Launch Clock 3) Tap create new alarm and press time selection 4) Scroll on minute or hour field Actual: Background screen flickers into view while scrolling. Expected: No flickering graphics appear on screen. Environmental Variables: Device: Xperia Z3 Compact (B2G) 3.0 Build ID: 20150602115822 Gaia: Unknown Gecko: 9eae3880b132 Version: 41.0a1 (3.0) User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0 Repro frequency: 3/3, 100% See attached: Youtube video clip - http://youtu.be/aeAzDngfMk0
I wasn't able to reproduce this issue after a while trying. Memory pressure and many opened programs did not help reproduce it. Leaving the steps-wanted tag for others to try it. Environmental Variables: Device: Aries 3.0 BuildID: 20150604140701 Gaia: dbf8e12660af79aa118ad1c32b2efc99f9a79c7b Gecko: 5b4c240e1a36 Gonk: 3af1ede0d0956cfbf9c549df7cd9a6807a9efdf2 Version: 41.0a1 (3.0) Firmware Version: D5803_23.1.A.1.28_NCB.ftf User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
Flags: needinfo?(ktucker)
Flags: needinfo?(ktucker)
Whiteboard: [3.0-Daily-Testing],[spark] → [3.0-Daily-Testing],[spark],[gfx-noted]
Status: NEW → RESOLVED
Closed: 11 years ago
QA Whiteboard: [QAnalyst-Triage+]
Keywords: steps-wanted
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.