Closed
Bug 911901
Opened 12 years ago
Closed 12 years ago
[WAP push] If exit wap push message via home key and open another push msg, content will be empty and title become "wap-push-message" and unable to close it.
Categories
(Firefox OS Graveyard :: Gaia, defect)
Tracking
(blocking-b2g:koi+, b2g-v1.2 fixed)
People
(Reporter: echu, Assigned: gsvelto)
References
Details
(Whiteboard: [FT:RIL])
Attachments
(2 files, 1 obsolete file)
If exit wap push message via home key and open another push msg, content will be empty and title become "wap-push-message" and unable to close it.
* Build Number
Gaia: 9fb5802df60a9081846d704def01df814ed8fbd4
Gecko: http://hg.mozilla.org/mozilla-central/rev/b6c29e434519
BuildID 20130901040215
Version 26.0a1
* Reproduce Steps
1. Send 2 wap push messages to DUT.(using NowSMS)
2. Open 1 message and press home key to exit it.
3. Open another one via drag down notification bar.
* Expected Result
Another content can be viewed.
* Actual Result
1. Content is empty.
2. Title is changed from sender's number to "wap-push-message".
* Occurrence rate
100%
Updated•12 years ago
|
blocking-b2g: koi? → koi+
Updated•12 years ago
|
Assignee: nobody → gsvelto
| Assignee | ||
Comment 2•12 years ago
|
||
This patch detects when the attention screen is shrunk into the status-bar (which happens when the home button is pressed) and closes it instead. The patch also ensures that the entire application closes itself when the attention screen is dismissed.
Attachment #802357 -
Flags: review?(21)
| Assignee | ||
Comment 3•12 years ago
|
||
Comment on attachment 802357 [details] [diff] [review]
[PATCH] Close the WAP Push attention screen when the home button is pressed
Awww... wrong bug, this should have been in bug 911895.
Attachment #802357 -
Attachment is obsolete: true
Attachment #802357 -
Flags: review?(21)
| Assignee | ||
Updated•12 years ago
|
Status: NEW → ASSIGNED
Hi Gabriele,
Is this fixed as well since bug 911895 is fixed now?
| Assignee | ||
Comment 5•12 years ago
|
||
(In reply to Enpei from comment #4)
> Is this fixed as well since bug 911895 is fixed now?
Not yet. I need a different code-path for this and I will refactor part of the app accordingly but I want to land bug 911247 before that.
| Assignee | ||
Comment 6•12 years ago
|
||
Quick update on this. Notifications were thoroughly broken so since I had to touch that code already in bug 911247 this will also be fixed as part of it (a patch is available there already that also fixes the issue).
This is not found on
Gaia: 313599c293f596519604070fa378ffc89e61e98f
Gecko: http://hg.mozilla.org/releases/mozilla-aurora/rev/decf58f0d596
BuildID 20131008004009
Version 26.0a2
but found some other bugs can still reproduce the issue.
| Assignee | ||
Comment 8•12 years ago
|
||
This was fixed as part of bug 911247.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Verified on Buri.
Gaia: d0f0110f6a907ef386134dc693f5dc5a632a0e9e
Gecko: http://hg.mozilla.org/releases/mozilla-aurora/rev/818ef9b4096c
BuildID 20131013004004
Version 26.0a2
Status: RESOLVED → VERIFIED
Updated•11 years ago
|
status-b2g-v1.2:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•