Bug 33242 – UMC Notifications: All notifications are shown when clicking on "i" while a new notification is still visible

Bug 33242 - UMC Notifications: All notifications are shown when clicking on "i" while a new notification is still visible


Summary:	UMC Notifications: All notifications are shown when clicking on "i" while a n...

Status:	RESOLVED DUPLICATE of bug 35654

Product:	UCS
Classification:	Unclassified
Component:	UMC (Generic)
Version:	UCS 3.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 3.2-x
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-11-11 13:06 CET by Dirk Wiesenthal
Modified:	2014-11-03 20:22 CET (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dirk Wiesenthal

2013-11-11 13:06:11 CET

If a new notification is added, it is visible for a couple of seconds. When clicking on "i" during this period, all (old + the new one) notifications are shown.

Expected behaviour: The new notification gets hidden. This is already the case when there are no old notifications, i.e. if the new notification was the very first one.

Comment 1 Alexander Kläser

2013-11-11 14:59:01 CET


*** This bug has been marked as a duplicate of bug 32997 ***

Comment 2 Alexander Kläser

2013-11-11 15:39:03 CET

(In reply to Alexander Kläser from comment #1)
> 
> *** This bug has been marked as a duplicate of bug 32997 ***

No duplicate anymore.

Comment 3 Florian Best

2014-11-03 20:22:24 CET

No such [i] icon anymore in UCS4.

*** This bug has been marked as a duplicate of bug 35654 ***