[MGNLUI-65] Retain "new" state of a message in Pulse for a short time, when you've click on it in a message band Created: 30/Aug/12 Updated: 03/Dec/13 Resolved: 03/Dec/13 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Andreas Weder | Assignee: | Mikaël Geljić |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | design | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
In SCRUM-1515, we've implemented a proper transition when clicking on a message band: Pulse opens and selects the affected message. It also immediately marks it as "read" and decreases the message count. This is actually a bit confusing. It would be more helpful, if the transition from the message band to the message being shown in Pulse would include a short delay in the message being read:
Like this, the state of the message is first what you'd expect, since you haven't read it yet. You then witness it being marked as "read". Note that, if Pulse is already open and you click on a message, it can be marked as read immediately. The delay only needs to be applied, if the message is "pre-selected" before being shown in Pulse. |
| Comments |
| Comment by Andreas Weder [ 30/Aug/12 ] |
|
|
| Comment by Mikaël Geljić [ 03/Dec/13 ] |
|
When clicking the MORE link, we now go to the message detail view instead of the list view. Only when going to this view the message is marked as read. Hence such delay currently no longer makes sense. |