Closed
Bug 912490
Opened 11 years ago
Closed 11 years ago
[Dialer] Invalid (zls) ID for section element on outgoing call screen
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: zcampbell, Assigned: etienne)
Details
Attachments
(2 files)
In an outgoing call, the section element that contains outgoing call information contains an element with a zls id attribute. In the attached source code, the offending line is line 72. As the ID is a zls I am getting the impression that something is supposed to be setting an ID to it but failing to do so somewhere. STR 1. Create a contact with first name, surname and phone number. 2. Load the contact details page in Contacts app 3. Tap 'call' to call the Contact 4. Wait for call to initiate 5. Dump/capture HTML
Assignee | ||
Comment 1•11 years ago
|
||
We can have more than one call, so an ID won't cut it. We can add a class to every handled call node pretty easily if this would solve your issue (we don't need it for anything else).
Reporter | ||
Comment 2•11 years ago
|
||
Yes that would resolve the problem etienne, thanks. This is making our automation tricky because there's no trustworthy locator.
Comment 5•11 years ago
|
||
Comment on attachment 799515 [details]
Pointer to gaia PR
I'd rather add the class when we copy the node so that this class only represents real calls.
Attachment #799515 -
Flags: review?(anthony) → review-
Assignee | ||
Comment 6•11 years ago
|
||
[:facepalm] indeed, it would be much better for the purpose of this bug :)
Assignee | ||
Comment 7•11 years ago
|
||
Comment on attachment 799515 [details]
Pointer to gaia PR
ready for the new round, thanks for saving my ass!
Attachment #799515 -
Flags: review- → review?(anthony)
Updated•11 years ago
|
Attachment #799515 -
Flags: review?(anthony) → review+
Assignee | ||
Comment 8•11 years ago
|
||
https://github.com/mozilla-b2g/gaia/commit/6b5420e59ddc0399735e09b177bc22902cdc6fb2
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•