Closed Bug 877123 Opened 11 years ago Closed 7 years ago

el.tap() sms notifier in status bar opens the wrong thread.

Categories

(Remote Protocol :: Marionette, defect)

Product:
Remote Protocol
Component:
Marionette
Platform:
Other
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: roy.collings, Unassigned)

References

Details

(Keywords: pi-marionette-userinput) 

User Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.63 Safari/537.31

Steps to reproduce:

Using build: unagi-ICS.eng.v1-train.Rel0.4.Sprint10.B-102.Gecko-489c6ee.Gaia-353c101

Send an sms to myself, then switch back to homescreen before the SMS arrives (so I get the statusbar notification).

Once the notification arrives (I get two: one from 'me' and one from '222000' saying I sent an sms), I expand the statusbar to see the notifications so they can be tapped.


Actual results:

If I use el.tap() on the notification it opens the correct thread, then closes it and opens the thread from 222000 (the message that reports you have sent a message).
If I use el.click() on the notification it opens the correct thread as expected.


Expected results:

The sms app should open and we should be taken to the correct thread for this number.
Depends on: 869034
Component: Gaia::SMS → Marionette
OS: All → Gonk (Firefox OS)
Product: Boot2Gecko → Testing
Hardware: All → Other
Blocks: 869034
No longer depends on: 869034
Whiteboard: [touch]
Keywords: ateam-marionette-userinput
Whiteboard: [touch]
[Mass closure] Closing as these features are no longer needed or wanted
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.