Closed Bug 1140153 Opened 9 years ago Closed 9 years ago

[STK] Icon format not compliant with the new data format of confirmMessage/callMessage from SET_UP_CALL/LAUNCH_BROWSER

Categories

(Firefox OS Graveyard :: Gaia, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:2.2+, b2g-v2.2 fixed, b2g-master fixed)

RESOLVED FIXED
2.2 S10 (17apr)
blocking-b2g 2.2+
Tracking Status
b2g-v2.2 --- fixed
b2g-master --- fixed

People

(Reporter: anshulj, Assigned: mancas)

References

Details

(Whiteboard: [caf priority: p2][CR 804218][ft:comms])

Attachments

(3 files)

In bug 1091454 the data format of confirmMessage/callMessage from SET_UP_CALL and LAUNCH_BROWSER proactive commands was changed but Gaia still doesn't support the new format, nor provides backwards compatibility for the icons.The functin STK_CMD_LAUNCH_BROWSER in icc_worker.js at [1] still uses options.icons instead of options.confirmMessage.icons.

[1] http://lxr.mozilla.org/gaia/source/apps/system/js/icc_worker.js#152
Summary: [STK] Icon display for new data format of confirmMessage/callMessage from SET_UP_CALL/LAUNCH_BROWSER is missing → [STK] Icon format not compliant with the new data format of confirmMessage/callMessage from SET_UP_CALL/LAUNCH_BROWSER
Whiteboard: [CR 804218]
Whiteboard: [CR 804218] → [caf priority: p2][CR 804218]
NI Bevis to help look at this.
blocking-b2g: 2.2? → 2.2+
Flags: needinfo?(btseng)
It seems that implementation in bug 1016807 didn't follow the format of MozStkSetUpCall & MozStkBrowserSetting defined in MozStkCommandEvent.webidl properly.

Where confirmMessage/callMessage in MozStkSetUpCall & MozStkBrowserSetting are defined as:
dictionary MozStkTextMessage : MozStkIconContainer
{
  DOMString text;
  MozStkDuration duration;
  boolean isHighPriority;
  boolean userClear;
  boolean responseNeeded;
};

dictionary MozStkIconContainer
{
  boolean iconSelfExplanatory;
  sequence<MozStkIcon> icons;
};

NI the assignee of bug 1016807 to check this instead.
Flags: needinfo?(btseng) → needinfo?(b.mcb)
No longer blocks: CAF-v3.0-FL-metabug
Whiteboard: [caf priority: p2][CR 804218] → [caf priority: p2][CR 804218][ft:comms]
Wesley, does it mean that this bug will be reviewed by Comms team who will try to find an owner? Thanks.
Flags: needinfo?(whuang)
Assignee: nobody → b.mcb
Flags: needinfo?(b.mcb)
Status: NEW → ASSIGNED
Comment on attachment 8578579 [details] [review]
[gaia] mancas:bug1140153 > mozilla-b2g:master

Now it should work as expected. Can you review this when you get a chance, Tim?

Anshul could you test and check if everything is ok?

Thanks =)
Attachment #8578579 - Flags: review?(timdream)
Attachment #8578579 - Flags: feedback?(anshulj)
Comment on attachment 8578579 [details] [review]
[gaia] mancas:bug1140153 > mozilla-b2g:master

Edgar, the original issue reported is resolved with your patch. However with your patch, the confirm message text is not displayed. Instead icc-confirmCall-defaultmessage is getting displayed. Please find the snapshots attached with and without your patch.
Attachment #8578579 - Flags: feedback?(anshulj) → feedback-
Comment on attachment 8578579 [details] [review]
[gaia] mancas:bug1140153 > mozilla-b2g:master

Good catch! It was my fault. Now, it should be fixed, would you mind testing it again please?
Attachment #8578579 - Flags: feedback- → feedback?(anshulj)
Comment on attachment 8578579 [details] [review]
[gaia] mancas:bug1140153 > mozilla-b2g:master

The patch seems to be working as expected.
Attachment #8578579 - Flags: feedback?(anshulj) → feedback+
Flags: needinfo?(whuang)
Looks like we have the fix, can we please land it asap.
Flags: needinfo?(b.mcb)
It needs to be reviewed first.

Tim, Manuel asked you to review this patch, can you have a look at it, please? Let's know if you can`t to look for another reviewer. Thanks
Flags: needinfo?(b.mcb) → needinfo?(timdream)
Comment on attachment 8578579 [details] [review]
[gaia] mancas:bug1140153 > mozilla-b2g:master

Is the code testable?
Flags: needinfo?(timdream)
Attachment #8578579 - Flags: review?(timdream) → review+
Keywords: checkin-needed
http://docs.taskcluster.net/tools/task-graph-inspector/#7qc4fnQmSs6VxCBpOHrUuQ

The pull request failed to pass integration tests. It could not be landed, please try again.
Hi Maria,

Please address the auto-land failure below:

(In reply to Autolander from comment #15)
> http://docs.taskcluster.net/tools/task-graph-inspector/
> #7qc4fnQmSs6VxCBpOHrUuQ
> 
> The pull request failed to pass integration tests. It could not be landed,
> please try again.


Thanks,
Mike
Flags: needinfo?(oteo)
Manu, can you have a look at the auto-lander failure that Mike points in comment 16? Thanks a lot!
Flags: needinfo?(oteo) → needinfo?(b.mcb)
Flags: needinfo?(b.mcb)
Keywords: checkin-needed
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2.2 S10 (17apr)
Comment on attachment 8578579 [details] [review]
[gaia] mancas:bug1140153 > mozilla-b2g:master

NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings.

[Approval Request Comment]
Bug caused by (feature/regressing bug #): 
User impact if declined: 
Testing completed: 
Risk to taking this patch (and alternatives if risky): 
String or UUID changes made by this patch:
Flags: needinfo?(bbajaj)
Attachment #8578579 - Flags: approval-mozilla-b2g37?
Flags: needinfo?(bbajaj)
Attachment #8578579 - Flags: approval-mozilla-b2g37? → approval-mozilla-b2g37+
Depends on: 1154439
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: