[B2G][Contacts] Scrolling in detail view of a contact with an image produces graphical issues showing layer below

RESOLVED FIXED

Status

defect
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: bzumwalt, Assigned: etienne)

Tracking

({regression})

unspecified
ARM
Gonk (Firefox OS)
Dependency tree / graph

Firefox Tracking Flags

(blocking-b2g:1.3+, b2g-v1.3 fixed)

Details

()

Attachments

(1 attachment)

46 bytes, text/x-github-pull-request
arcturus
: review+
Details | Review
Description:
In the contact app, when user is in the detailed view of a contact with an image associated with the individual, scrolling down (to reveal more of the associated image) then rapidly dragging finger up page reveals main contact list beneath detail view layer. This graphics issue occurs only with APZ enabled.

Repro Steps:
1) Updated Buri to BuildID: 20140128040224
2) Ensure APZ is enabled in settings (Settings>Device Information>More Information>Developer)
2) Open contact app (with multiple contacts already in list)
3) Tap existing contact that has an picture associated with the individual
4) Drag finger down screen, revealing more of the image header
5) Scroll up rapidly, observing bottom of screen while doing so

Actual:
Scrolling in detail view of contact reveals layer below.

Expected:
Scrolling in detail view of contact produces no graphical issues.

Environmental Variables:
Device: Buri v1.4 Master Mozilla RIL
BuildID: 20140128040224
Gaia: 6586d2b8b43c6997be5cf5895bbdf3dd20490725
Gecko: 4da3e21a0e5f
Version: 29.0a1
Firmware Version: V1.2-device.cfg

Notes:
Repro frequency: 3/3, 100%
See attached: video clip
Issue also occurs in latest 1.3

Result:
Scrolling in detail view of contact reveals layer below.

Environmental Variables:
Device: Buri v1.3 Mozilla RIL
BuildID: 20140128004000
Gaia: 3c5119507a985c59cfc264ed23821679b138486d
Gecko: 4936f09590a0
Version: 28.0a2
Firmware Version: V1.2-device.cfg
Does this reproduce with APZC disabled? Does this reproduce on 1.1?
Keywords: qawanted
Issue only occurs with APZC enabled. Issue does not occur with APZC disabled.
Blocks: gaia-apzc
Component: Gaia::Contacts → Panning and Zooming
Keywords: qawantedregression
Product: Firefox OS → Core
Version: unspecified → 28 Branch
blocking-b2g: --- → 1.3?
Blocks: 942267
blocking-b2g: 1.3? → 1.3+
Botond, could you look into this one?
Assignee: nobody → botond
(In reply to Brogan Zumwalt from comment #3)
> Issue only occurs with APZC enabled. Issue does not occur with APZC disabled.

Hmm. I see this issue with both APZC enabled and APZC disabled. Tested with Buri running 1.3 and Nexus 4 running master, same results.
(In reply to Botond Ballo [:botond] from comment #5)
> (In reply to Brogan Zumwalt from comment #3)
> > Issue only occurs with APZC enabled. Issue does not occur with APZC disabled.
> 
> Hmm. I see this issue with both APZC enabled and APZC disabled. Tested with
> Buri running 1.3 and Nexus 4 running master, same results.

Actually, there is a difference: with APZC off, I have to _fling_ to see the underlying layers. With APZC on, _panning_ sufficiently quickly exposes them as well.
Sounds like an issue with the contacts app then? More importantly it means we should be able to get a regression window of when it started happening, which presumably will be not when APZC was turned on.
I can also see this with APZC disabled on the latest 1.3 code on Hamachi. Bouncing back to Gaia team.
Assignee: botond → nobody
Component: Panning and Zooming → Gaia::Contacts
Product: Core → Firefox OS
Version: 28 Branch → unspecified
I can reproduce it, having a look...
Assignee: nobody → etienne
Posted file Gaia PR
Sweet and simple.
Attachment #8368677 - Flags: review?(francisco.jordano)
Comment on attachment 8368677 [details] [review]
Gaia PR

Hardest review ever!

Thanks Etienne for taking care of this
Attachment #8368677 - Flags: review?(francisco.jordano) → review+
https://github.com/mozilla-b2g/gaia/commit/4470879d2fec6c6344e72e7390632923eba224d6
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
I was not able to uplift this bug to v1.3.  If this bug has dependencies which are not marked in this bug, please comment on this bug.  If this bug depends on patches that aren't approved for v1.3, we need to re-evaluate the approval.  Otherwise, if this is just a merge conflict, you might be able to resolve it with:

  git checkout v1.3
  git cherry-pick -x -m1 4470879d2fec6c6344e72e7390632923eba224d6
  <RESOLVE MERGE CONFLICTS>
  git commit
Flags: needinfo?(etienne)
You need to log in before you can comment on or make changes to this bug.