Closed
Bug 1187832
Opened 9 years ago
Closed 9 years ago
[B2G][ICC] Do not notify for "SEND XXX" STK commands when the alpha identifier is a null object.
Categories
(Firefox OS Graveyard :: RIL, defect)
Tracking
(firefox43 fixed)
RESOLVED
FIXED
FxOS-S5 (21Aug)
Tracking | Status | |
---|---|---|
firefox43 | --- | fixed |
People
(Reporter: freesamael, Assigned: freesamael)
References
Details
Attachments
(1 file, 2 obsolete files)
22.85 KB,
patch
|
bevis
:
review+
|
Details | Diff | Splinter Review |
According to |6.4.10 SEND SHORT MESSAGE| of |ETSI TS 102 223| [1], the notification shouldn't be brought up to the user if the alpha identifier is a null object. > * if the alpha identifier is provided by the UICC and is a null data object (i.e. length = '00' > and no value part), this is an indication that the terminal should not give any information to > the user on the fact that the terminal is sending a short message; > > * if the alpha identifier is not provided by the UICC, the terminal may give information to the > user concerning what is happening. The same behavior applies to "Send DTMF", "Send SS", and "Send USSD". The current implementation kind of mixed up the cases of "alpha identifier is not provided" and "alpha identifier is a null object", and triggers notifications incorrectly. We should avoid sending system messages if the alpha identifier is a null object. [1] http://www.etsi.org/deliver/etsi_ts/102200_102299/102223/12.02.00_60/ts_102223v120200p.pdf
Comment 1•9 years ago
|
||
Udpate bug title because STK commands are delivered over both dom events and system messages.
Summary: [B2G][ICC] Do not send system messages for "SEND XXX" STK commands when the alpha identifier is a null object. → [B2G][ICC] Do not notify for "SEND XXX" STK commands when the alpha identifier is a null object.
Assignee | ||
Comment 2•9 years ago
|
||
Assignee | ||
Comment 3•9 years ago
|
||
Assignee | ||
Updated•9 years ago
|
Attachment #8642339 -
Attachment description: Update ril_worker and corresponding test cases → (v2) Update ril_worker and corresponding test cases
Assignee | ||
Updated•9 years ago
|
Attachment #8641508 -
Attachment is obsolete: true
Assignee | ||
Comment 4•9 years ago
|
||
Assignee | ||
Updated•9 years ago
|
Attachment #8642867 -
Attachment description: Update ril_worker and corresponding test cases → (v3) Update ril_worker and corresponding test cases
Assignee | ||
Updated•9 years ago
|
Attachment #8642339 -
Attachment is obsolete: true
Assignee | ||
Comment 5•9 years ago
|
||
Comment on attachment 8642867 [details] [diff] [review] (v3) Update ril_worker and corresponding test cases Hi Bevis, Could you help to review the patch?
Attachment #8642867 -
Flags: review?(btseng)
Comment 6•9 years ago
|
||
Comment on attachment 8642867 [details] [diff] [review] (v3) Update ril_worker and corresponding test cases Review of attachment 8642867 [details] [diff] [review]: ----------------------------------------------------------------- Please see my comment inline. ::: dom/system/gonk/ril_worker.js @@ +9692,5 @@ > + if (textMsg.text !== "") { > + // Icon identifier is optional. > + this.appendIconIfNecessary(selectedCtlvs[COMPREHENSIONTLV_TAG_ICON_ID] || null, > + textMsg, > + onComplete); We should not suppress the notification of the user case that the alphaId is not available but the icon is available to be displayed. Please also have this user case available in our test coverage. Thanks!
Attachment #8642867 -
Flags: review?(btseng)
Comment 7•9 years ago
|
||
Comment on attachment 8642867 [details] [diff] [review] (v3) Update ril_worker and corresponding test cases Review of attachment 8642867 [details] [diff] [review]: ----------------------------------------------------------------- Per offline discussion, It seems to be my misunderstanding. The availability of AlphaId is the first priority to display this notification according to the standard. Thanks!
Attachment #8642867 -
Flags: review+
Assignee | ||
Updated•9 years ago
|
Keywords: checkin-needed
https://hg.mozilla.org/mozilla-central/rev/a29e9b59c7f5
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox43:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → FxOS-S5 (21Aug)
You need to log in
before you can comment on or make changes to this bug.
Description
•