Closed
Bug 1044406
Opened 10 years ago
Closed 10 years ago
Tap on notification does nothing
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(blocking-b2g:2.1+, b2g-v2.1 verified)
Tracking | Status | |
---|---|---|
b2g-v2.1 | --- | verified |
People
(Reporter: gerard-majax, Assigned: cwiiis)
References
Details
(Keywords: regression, smoketest, Whiteboard: [systemsfe])
Attachments
(1 file, 1 obsolete file)
With current master on my Nexus S, tapping on a notification does nothing.
STR:
0. Receive a SMS
1. Pull down notification tray
2. Tap SMS notification
Expected:
Messages application gets launched.
Actual:
Nothing happens.
Reporter | ||
Comment 1•10 years ago
|
||
Doing a local revert of bug 1041383 fixes the regression for me.
Depends on: 1041383
Flags: needinfo?(chrislord.net)
Assignee | ||
Comment 2•10 years ago
|
||
Whoops - I should've tested better after removing GestureDetector in my original patch. I don't think using GestureDetector just for a tap makes sense so I've implemented it in the existing touch handling.
Assignee: nobody → chrislord.net
Status: NEW → ASSIGNED
Attachment #8463382 -
Flags: review?(mhenretty)
Flags: needinfo?(chrislord.net)
Comment 3•10 years ago
|
||
Comment on attachment 8463382 [details] [review]
Don't listen to 'tap' event without GestureDetector
As I was fixing bug 1007413 (which it became a dup of this), be careful with tests, they should fail with your current solution because you removed the `tap` event.
IMHO, you could emit a synthetic `tap` event instead of calling .tap() in `touchend` and restore the `tap` case. This way, the behaviour remains almost unaltered but you get rid of all the complexity from GestureDetector.
Blocks: 1038262
Updated•10 years ago
|
blocking-b2g: 2.1? → 2.1+
Comment 6•10 years ago
|
||
Alex, can you take a look? There are two commits in this PR because I wanted to preserve credit/blame for the different pieces.
Attachment #8463382 -
Attachment is obsolete: true
Attachment #8463382 -
Flags: review?(mhenretty)
Attachment #8463687 -
Flags: review?(lissyx+mozillians)
Reporter | ||
Comment 7•10 years ago
|
||
Comment on attachment 8463687 [details] [review]
Gaia PR, use tap event without Gesture Detector
Thanks, it works well when testing this. I'm happy that we can re-enable some tests, but can we ensure that they do not trigger new intermittence?
Attachment #8463687 -
Flags: review?(lissyx+mozillians) → review+
Comment 8•10 years ago
|
||
master: https://github.com/mozilla-b2g/gaia/commit/ec80df3247ef00d5382c59255a5e46b5d45494e6
(In reply to Alexandre LISSY :gerard-majax from comment #7)
> Comment on attachment 8463687 [details] [review]
> Gaia PR, use tap event without Gesture Detector
>
> Thanks, it works well when testing this. I'm happy that we can re-enable
> some tests, but can we ensure that they do not trigger new intermittence?
Yeah, we will have to watch this test and make sure it does not trigger new intermittents. But, we absolute need this test to avoid smoke test regressions like this bug.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
status-b2g-v2.1:
--- → fixed
Target Milestone: --- → 2.1 S1 (1aug)
I just pulled today's gaia and this is fixed.
Status: RESOLVED → VERIFIED
Comment 10•10 years ago
|
||
Adding smoketest keyword.
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
Updated•10 years ago
|
Whiteboard: [systemsfe]
Comment 11•10 years ago
|
||
Verified as fixed in Flame 2.1
Tapping sms notifications opens the messaging app appropriately.
Environmental Variables:
Device: Flame 2.1
BuildID: 20141021001201
Gaia: e458f5804c0851eb4e93c9eb143fe044988cecda
Gecko: ee86921a986f
Gonk: 05aa7b98d3f891b334031dc710d48d0d6b82ec1d
Version: 34.0 (2.1)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
Assignee | ||
Updated•10 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•