Closed Bug 1082936 Opened 10 years ago Closed 10 years ago

STK messages are seen overlapping each other

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

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

RESOLVED FIXED
2.2 S2 (19dec)
blocking-b2g 2.2+
Tracking Status
b2g-v2.1 --- wontfix
b2g-v2.2 --- fixed

People

(Reporter: anshulj, Assigned: mancas)

References

Details

(Whiteboard: [caf priority: p2][CR 741217])

Attachments

(3 files)

Attached image overlapping_stk_text
[Blocking Requested - why for this release]: Poor user experience STR: 1. Send a STK proactive command SEND_SMS with some text, for example "Send SM" 2. Send another STK proactive command SEND_SMS or SEND_DTMF with some text, for example "Send DTMF". Expected: UI should show the first message followed by the second message. Observed: Both of the messages are visible on the top of each other. Please check the attachment.
Flags: needinfo?(frsela)
2.1 CC blocker = 2.1+.
blocking-b2g: 2.1? → 2.1+
Whiteboard: [CR 741217]
Whiteboard: [CR 741217] → [caf priority: p2][CR 741217]
Currently STK messages are not piped and attended as soon as they're received. From my point of view this is a new feature, isn't it?
Flags: needinfo?(frsela)
Fernando, by message not being piped due to mean not queued such that the next message is behind the previous message in the display order? Can we simply not clear the previous message before displaying the next one?
ni? to Fernando for comment 3.
Flags: needinfo?(frsela)
(In reply to Anshul from comment #3) > Fernando, by message not being piped due to mean not queued such that the > next message is behind the previous message in the display order? > > Can we simply not clear the previous message before displaying the next one? Hi Anshul, I mean both. Messages are not queued, so they are attended as they arrive. This is the first point of improve. Also the Alerts, Input boxes, etc. use the same DIV [1] (showing or hiding it) so we can not display over the other one since each STK message is replacing the div content. This is the second point of improve ;) [1] https://github.com/mozilla-b2g/gaia/blob/master/apps/system/index.html#L1115
Flags: needinfo?(frsela)
Assignee: nobody → b.mcb
:mancas, given comment #5, what is the effort required to resolve this in time to hit the 2.1 dates? In terms of timeline we are exactly a week away in fixing CAF 2.1 CC bugs.
Flags: needinfo?(b.mcb)
Attached file Messages are piped
Attachment #8510877 - Flags: review?(timdream)
Attachment #8510877 - Flags: feedback?(frsela)
I think we can resolve this in time...The first approach of the patch is done, but we need to review it, and make changes if needed. So until the first revision I can't give you an estimated date.
Flags: needinfo?(b.mcb) → needinfo?(bbajaj)
Comment on attachment 8510877 [details] [review] Messages are piped f+ but with nits
Attachment #8510877 - Flags: feedback?(frsela) → feedback+
Comment on attachment 8510877 [details] [review] Messages are piped r+ since :frsela have feedback+'d the patch.
Attachment #8510877 - Flags: review?(timdream) → review+
Attached file Patch v2.1
[Approval Request Comment] [Bug caused by] (feature/regressing bug #): New feature [User impact] if declined: The user will see the STK messages overlapped [Testing completed]: Yes [Risk to taking this patch] (and alternatives if risky): Low [String changes made]:No
Attachment #8513355 - Flags: approval-gaia-v2.1?
Flags: needinfo?(bbajaj)
Attachment #8513355 - Flags: approval-gaia-v2.1? → approval-gaia-v2.1+
Unable to verify as it is a back-end issue.
QA Whiteboard: [QAnalyst-Triage?][QAnalyst-verify-]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage?][QAnalyst-verify-] → [QAnalyst-Triage+][QAnalyst-verify-]
Flags: needinfo?(ktucker)
Depends on: 1095802
Reverted on commit 6a24c8e4564432c804931ed85346f73425cf5290 Follow up in bug 1095802
Reverted also in branch 2.1: 8495c5ebac772bba2b3b95f6f1e5c46b753ef7f4
Thanks for the backout, lets track these issues for 2.2 per : https://bugzilla.mozilla.org/show_bug.cgi?id=1095802#c14
blocking-b2g: 2.1+ → 2.2+
Target Milestone: 2.1 S8 (7Nov) → 2.2 S2 (19dec)
Attachment #8513355 - Flags: approval-gaia-v2.1+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: