Closed Bug 1036676 Opened 11 years ago Closed 6 years ago

[B2G][Camera] A vertical strip of wallpaper is showing while changing between photos on Preview mode.

Categories

(Core :: Graphics, defect)

Other Branch
ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX
Tracking Status
b2g-v1.4 --- unaffected
b2g-v2.0 --- affected
b2g-v2.1 --- affected

People

(Reporter: ychung, Unassigned)

References

()

Details

(Keywords: regression, Whiteboard: [273MB-Flame-Support] [2.0-exploratory])

Attachments

(1 file)

Description: When the user swipes through between photos on the preview mode in the Camera app, parts of the wallpaper from the Homescreen are showing. Repro Steps: 1) Updated Flame to Build ID: 20140708000322 2) Make sure the Flame device is set to 273mb. 3) Open Camera app, and take multiple photos (over 10). 4) Select the preview icon, and swipe through the photos. Actual: Parts of the wallpaper from the Homescreen are showing while changing between photos. Expected: The photos are changing smoothly without showing parts of the wallpaper. Flame 2.0 (273mb) Environmental Variables: Device: Flame 2.0 BuildID: 20140708000322 Gaia: e935f4ff190b76c70d9b2af8856c542a6e4a7546 Gecko: 3f9d7a3a0b7b Version: 32.0a2 (2.0) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Repro frequency: 100% See attached: Video, logcat https://www.youtube.com/watch?v=PTXEvD24CFY&edit=vd
This issue also reproduces on the Flame 2.1(273mb), Flame 2.0 (512mb), Buri 2.1, Buri 2.0: Flame 2.1 (273mb) Environmental Variables: Device: Flame Master BuildID: 20140709040203 Gaia: 0f9f11d0a6dadb3ea27160204bbe911c1ad69a6f Gecko: 196d05832e12 Version: 33.0a1 (Master) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0 Flame 2.0 (512mb) Environmental Variables: Device: Flame 2.0 BuildID: 20140708000322 Gaia: e935f4ff190b76c70d9b2af8856c542a6e4a7546 Gecko: 3f9d7a3a0b7b Version: 32.0a2 (2.0) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Buri 2.1 Environmental Variables: Device: Buri Master Build ID: 20140709073020 Gaia: c394b7b4205b6f1a6ca44915fc08650f3ad127ec Gecko: 2d88803a0b9c Version: 33.0a1 (Master) Firmware Version: v1.2device.cfg User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0 Buri 2.0 Environmental Variables: Device: Buri 2.0 Build ID: 20140709063007 Gaia: 1774027323bb072b4ebdfea9883572bcf2535c87 Gecko: 11b6493a7d8f Version: 32.0a2 (2.0) Firmware Version: v1.2device.cfg User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Parts of the wallpaper from the Homescreen are showing while changing between photos. --------------------------------------------------------------------------------------------- This issue does NOT reproduce on the Flame 1.4 (273mb): Flame 1.4 (273mb) Environmental Variables: Device: Flame 1.4 Build ID: 20140709003002 Gaia: b0e9b4bdb39c5eb93a6783a34624ffc84f62b126 Gecko: acf704e54e19 Version: 30.0 (1.4) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 The photos are changing smoothly without showing parts of the wallpaper.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Does this issue occur on 1.4 Buri?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage-]
Flags: needinfo?(ktucker) → needinfo?(ychung)
This issue does NOT reproduce on Buri 1.4: Buri 1.4 Environmental Variables: Device: Buri 1.4 Build ID: 20140709003002 Gaia: b0e9b4bdb39c5eb93a6783a34624ffc84f62b126 Gecko: acf704e54e19 Version: 30.0 (1.4) Firmware Version: v1.2device.cfg User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 The photos are changing smoothly without showing parts of the wallpaper.
Flags: needinfo?(ychung)
From bug 1036668: I'm guessing edge gestures conflicting with previous/next picture gestures?
Flags: needinfo?(dflanagan)
This is missing a QAnalyst-Triage? flag
Flags: needinfo?(ychung)
QA Whiteboard: [QAnalyst-Triage-] → [QAnalyst-Triage?]
Flags: needinfo?(ychung)
Also - don't forget to needinfo your lead.
Flags: needinfo?(ychung)
Flags: needinfo?(ychung) → needinfo?(ktucker)
Please add the regression keyword here.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage-]
Flags: needinfo?(ktucker) → needinfo?(ychung)
QA Whiteboard: [QAnalyst-Triage-] → [QAnalyst-Triage?]
Flags: needinfo?(ychung) → needinfo?(ktucker)
Keywords: regression
This is regression from 1.4 but this appears to a minor visual issue especially on the latest 2.0 build.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage+]
The attached video is pretty weird. I suspect that Mike is right in comment #5 that this is a strange interaction with edge gestures... The gesture begins as an edge gesture and then ends up swiping a photo, but the little strip of edge is dragged along with the animating photo? Needinfo Vivien who might know about this or will know who to ask... Vivien: have you seen anything like this before? I don't think this happens in gallery, but in gallery we have three side by side screens are are animating a new photo on when we animate the old one off. In this case we're animating the entire element off the screen possibly leaving an empty <body> element displayed. Or maybe this is a graphics bug? Needinfo Milan in case he has any ideas. Note that despite the whiteboard, this bug apparently reproduces on high memory devices, too.
Flags: needinfo?(milan)
Flags: needinfo?(dflanagan)
Flags: needinfo?(21)
Needinfo Justin and Diego as well in case this is something we need to fix or work around in the camera.
Flags: needinfo?(jdarcangelo)
Flags: needinfo?(dmarcos)
(In reply to David Flanagan [:djf] from comment #10) > The attached video is pretty weird. > > I suspect that Mike is right in comment #5 that this is a strange > interaction with edge gestures... The gesture begins as an edge gesture and > then ends up swiping a photo, but the little strip of edge is dragged along > with the animating photo? > I would have expected the whole app to move with the gesture is it was edge gesture. Can you disable edge-gesture an see it you can reproduce ? (Setting name: edgesgesture.enabled). But I would vote for a gfx bug :)
Flags: needinfo?(21)
I imagine there are conflicts with gallery and edge swiping - lets see what the answer is to Vivien's question. I would expect any graphics issues to be wrong on the whole tile, and while the first time this fails (~0:02) it looks like a whole tile, other fails seem to be a lot narrower.
UX - Is this is a blocker from a UX perspective?
Flags: needinfo?(firefoxos-ux-bugzilla)
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
If this is a regression (which it seems to be) it is a blocker. We did some work on fixing conflicts with edge gestures and gallery earlier, I thought; I feel like I haven't seen them in a while, but the video implies they're back.
Flags: needinfo?(firefoxos-ux-bugzilla)
Stephany - Can you set the blocking nomination flag if you think it's worth nominating?
Flags: needinfo?(swilkes)
Also notice that this is not a camera bug. This has to be moved to the proper component: Is it Core::Graphics?
Flags: needinfo?(dmarcos) → needinfo?(jsmith)
(In reply to Diego Marcos [:dmarcos] from comment #17) > Also notice that this is not a camera bug. This has to be moved to the > proper component: Is it Core::Graphics? Maybe? I agree it's not a camera bug at least. Let's move it to gfx for now though since that's the next place the regression is suspected to be coming from.
Component: Gaia::Camera → Graphics
Flags: needinfo?(jsmith)
Product: Firefox OS → Core
[Blocking Requested - why for this release]: (In reply to Jason Smith [:jsmith] - At Work Week, Slow to Respond from comment #16) > Stephany - Can you set the blocking nomination flag if you think it's worth > nominating? Actually I'll take care of the flag. Nominating to block 2.0 for being a regression and a blocker for visual UX in 2.0.
blocking-b2g: --- → 2.0?
Flags: needinfo?(swilkes)
QA Whiteboard: [QAnalyst-Triage+][lead-review+]
blocking-b2g: 2.0? → 2.0+
(In reply to Stephany Wilkes from comment #15) > If this is a regression (which it seems to be) it is a blocker. We did some > work on fixing conflicts with edge gestures and gallery earlier, I thought; > I feel like I haven't seen them in a while, but the video implies they're > back. not necessarily - this bug got a little 'held up' in the writing process being passed back and forth and forgetting tags. The issue is now almost 3 weeks old so I think your initial thought was correct. Also - this was initially written in 273 mem and has yet to be retested on 319 mb, which I just did and the issue DOES NOT repro in Flame 2.0 or Flame 2.1 Actual results - out of 200 swipes (per build) i did not see the homescreen 'leak through' Environmental Variables: Device: Flame Master Build ID: 20140729063151 Gaia: 449d632c69b1a4bd5101d07d18f76799d3fd5f38 Gecko: 2fc48871c459 Version: 34.0a1 (Master) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Device: Flame 2.0 Build ID: 20140729050146 Gaia: cfc4d71c36c6e9f6731f2060427f80e2996bc066 Gecko: 3c91cce0d473 Version: 32.0 (2.0) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 -------------------------------------------------------------------------------------------- This could possibly be considered works-for-me but I'm going to follow the 273-319 mem retest flow for now. Unblocking and leaving open for perf investigation
blocking-b2g: 2.0+ → ---
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Flags: needinfo?(milan)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Flags: needinfo?(jdarcangelo)
Version: unspecified → Other Branch
Closing as we are not working on Firefox OS anymore.
Status: NEW → RESOLVED
Closed: 6 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: