Closed Bug 1170863 Opened 7 years ago Closed 7 years ago

[Aries] Touches on device screen edges are unresponsive


(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect, P1)

Gonk (Firefox OS)


(Not tracked)



(Reporter: drs, Assigned: etienne)



(Whiteboard: [spark])


(1 file)

46 bytes, text/x-github-pull-request
: review+
Details | Review
On the Aries (Z3C) device, touches near the edge of the screen are very unresponsive. For example, in the Gmail app, touching buttons near the edges is very difficult.

I suspect that this is an issue with edge gestures, but I don't have any way to verify this.
Etienne, could you take a look at this? I think you have an Aries device.
Flags: needinfo?(etienne)
I'm wondering how does the touch surface compares to the flame since edges are smaller.
There's at least one place where we don't take the dpi into account, working on a patch.
Might not be the only issue though, still investigating.
Flags: needinfo?(etienne)
Attached file GaiaPR
This is helping a lot.
I still get the odd issue from time to time where taping at the very very edge of the screen will trigger an active state (testing in email) but not open the thread. But I triple checked and we're forwarding all the right events so it's either app or apz related, and far less severe than what we have without this patch.

Alive, I know there's a lot going on, and this will cause a small conflict with the new bootup procedure patch :/ But it's a simple patch and it should actually fix the issue you had with this test file.
Assignee: nobody → etienne
Attachment #8614615 - Flags: review?(alive)
See Also: → 1170357
See Also: → 1171235
I will come back to this once bug 1171235 lands.
Flags: needinfo?(drs)
Comment on attachment 8614615 [details] [review]

I just landed the bootstrap so you may need to rebase. Maybe it will be backout-ed again then I will do.
Attachment #8614615 - Flags: review?(alive) → review+
Closed: 7 years ago
Resolution: --- → FIXED
Flags: needinfo?(drs)
You need to log in before you can comment on or make changes to this bug.