Closed
Bug 911940
Opened 11 years ago
Closed 11 years ago
[WAP push] When SI is expired after received it, there is no indicator or wording shows that it's expired.
Categories
(Firefox OS Graveyard :: Gaia, defect)
Tracking
(blocking-b2g:koi+)
RESOLVED
DUPLICATE
of bug 911934
blocking-b2g | koi+ |
People
(Reporter: echu, Assigned: gsvelto)
References
Details
(Whiteboard: [FT:RIL, burirun2])
Attachments
(2 files)
When SI is expired after received it, there is no indicator or wording shows that it's expired. Please refer to UX doc. * Build Number Gaia: 9fb5802df60a9081846d704def01df814ed8fbd4 Gecko: http://hg.mozilla.org/mozilla-central/rev/b6c29e434519 BuildID 20130901040215 Version 26.0a1 * Reproduce Steps 1. Send SI with SI Expires value 2013-09-05-T03:33:33Z from NowSMS to DUT. (later than the date of the test) 2. After receive the message, change device data and time later than the expire date. 3. open the message. * Expected Result "This message was expired" in the content of the message and URL cannot be tapped. * Actual Result No expired words. * Occurrence rate 100%.
Updated•11 years ago
|
blocking-b2g: koi? → koi+
Updated•11 years ago
|
Assignee: nobody → gsvelto
Assignee | ||
Comment 2•11 years ago
|
||
This is being addressed as part of bug 911934. The WIP patch on that bug implements the correct behavior according to the spec.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•