Closed Bug 876641 Opened 11 years ago Closed 11 years ago

Cannot remove contact from SMS using Marionette.

Categories

(Firefox OS Graveyard :: Gaia::SMS, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: roy.collings, Unassigned)

References

Details

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.master.Rel0.4.Sprint10.B-9.Gecko-5169c0a.Gaia-b109a9c

Open SMS app.
Create a new SMS.
Add a contact to the 'To:' field.
Try to tap the target name in the To field to remove it.


Actual results:

Nothing.

el.tap() and marionette.tap(el) show no change to the UI.
el.click() just removes the 'button' of the target name, leaving the target name looking like flat text.

None of the above approaches succeed in presenting the confirmation dialog for removing the target (when watching the test run - also confirmed by dumping a screenshot of every frame after this event).

The target is stored in a 1-level 'span' element, i.e. it's the only thing to 'tap'. To paraphrase:
<section id="messages-recipients-list">
   <span ... data-name="John Smith" ...>
   <span ... data-name="Bob Smith" ...>
</section>



Expected results:

A confirmation dialog should appear asking if we want to remove this target.
If you add a target contact by number, then when you tap it manually it just turns into a text field that you can edit manually.
To remove a target contact by just tapping the name, you have to add the contact by name.
Blocks: 869034
Working now - I haven't re-tested this is a while so I'm not sure at what point it started working for me, but my current build is:

unagi-ICS.eng.v1-train.Rel0.4.Sprint12.B-157.Gecko-2d17cfb.Gaia-773a197
Marking this as WFM; thanks for reporting back, Roy!  (Do you need Bugzilla permissions?)
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Thanks Stephen, I got permissions a few days ago (but I forgot about this bug ;).
You need to log in before you can comment on or make changes to this bug.