Closed Bug 1081570 Opened 11 years ago Closed 7 years ago

[Camera] Switching between the Camera and Video buttons rapidly can disable them

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(tracking-b2g:backlog, b2g-v2.1 unaffected, b2g-v2.2 affected)

RESOLVED WONTFIX
tracking-b2g backlog
Tracking Status
b2g-v2.1 --- unaffected
b2g-v2.2 --- affected

People

(Reporter: rkunkel, Unassigned)

References

Details

(Whiteboard: [priority])

Attachments

(1 file)

Attached file logcat
Description: After the user begins switching rapidly between the Video and Camera buttons the buttons will not be selectable. Repro Steps: 1) Update a Flame to 20141011040204 2) Launch the Camera app 3) Press the Video and Camera toggle button Rapidly Actual: The Camera and Video buttons become disabled. Expected: It is expected that the Camera and Video buttons can still be selected even after switching quickly between the two. Environmental Variables: ---------------------------------------- Device: Flame 2.2 Master BuildID: 20141011040204 Gaia: 95f580a1522ffd0f09302372b78200dab9b6f322 Gecko: 3f6a51950eb5 Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf Version: 35.0a1 (2.2 Master) Firmware: V180 User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0 Repro frequency: 100% See attached: Logcat
I am unable to reproduce this issue on the latest 2.1 Flame build: Environmental Variables: ---------------------------------------- Device: Flame 2.1 BuildID: 20141011000201 Gaia: f5d4ff60ffed8961f7d0380ada9d0facfdfd56b1 Gecko: d813d79d3eae Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf Version: 34.0a2 (2.1) Firmware: V180 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Tapping on the camera / video toggle for 30+ seconds in rapid succession does not cause the camera app to become unresponsive.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
This bug fails verification of bug 1061996
This is not a regression. A fix was uplifted to 2.1 and 2.2 but the fix did not work on 2.2 so a new issue was written. Please see bug 1061996
blocking-b2g: --- → 2.2?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage-]
Flags: needinfo?(ktucker) → needinfo?(rkunkel)
Nominating this 2.2? since this was a 2.1 blocker plus the user should never lose functionality.
Flags: needinfo?(rkunkel)
QA Whiteboard: [QAnalyst-Triage-] → [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Wilson, ni?-ing you since you worked on bug 1061996, mentioned in comment 3.
Flags: needinfo?(wilsonpage)
Afraid I don't have spare capacity at the moment. Justin is familiar with this issue.
Flags: needinfo?(wilsonpage) → needinfo?(jdarcangelo)
Whiteboard: [priority]
Will be addressed in 2.2, assigning to Justin
Assignee: nobody → jdarcangelo
blocking-b2g: 2.2? → backlog
Flags: needinfo?(jdarcangelo)
blocking-b2g: backlog → ---
Not working on this. Unassigning myself.
Assignee: jdarcangelo → nobody
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: