Closed
Bug 1141014
Opened 10 years ago
Closed 8 years ago
[Messages] Improve handling of notification "close" system message
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: azasypkin, Unassigned)
References
Details
Currently when user removes notification, System fires system "notification" message to notify Messages app that notification is removed. If Messages app hasn't been run before, System runs it to handle system message.
Essentially it maybe a waste of resources if user isn't going to use Messages app any time soon after notification was removed:
1. run application;
2. load all threads from IndexedDB;
3. render all threads.
If we start working on this bug after bug 1139363 is resolved, then the only thing we should do is to remove code that handles notification "close" system message here [1];
Otherwise we should try to at least initialize default panel only when user is going to access it (delay #2 and #3 from the list above). One of the ideas is to load and render default panel only when app becomes visible. We should explore this even though it may be tricky or not feasible at all.
[1] https://github.com/mozilla-b2g/gaia/pull/28491/files#diff-c4a4a1fb8874a8e40d0ebec5b8047224R521
Comment 1•8 years ago
|
||
Mass closing of Gaia::SMS bugs. End of an era :(
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Comment 2•8 years ago
|
||
Mass closing of Gaia::SMS bugs. End of an era :(
You need to log in
before you can comment on or make changes to this bug.
Description
•