Closed
Bug 1946707
Opened 10 months ago
Closed 10 months ago
Replacing notification with tag fires events with different order on libnotify; show happens before close
Categories
(Core :: Widget: Gtk, defect)
Core
Widget: Gtk
Tracking
()
RESOLVED
FIXED
137 Branch
| Tracking | Status | |
|---|---|---|
| firefox137 | --- | fixed |
People
(Reporter: saschanaz, Assigned: saschanaz)
References
Details
Attachments
(1 file)
Same as bug 1890560, but for libnotify backend. nsAlertsIconListener in this case defers calling alertfinish until it gets the close signal from the system, but given we call alertshow immediately after calling notify command, repeated opening of same-tagged notification causes wrong order of event (alertshow fires first while alertfinish waits for the system). Given we don't have a way to asynchronously wait for system for alertshow, we should immediately call alertfinish to make it consistent with alertshow.
| Assignee | ||
Comment 1•10 months ago
|
||
This will let Linux pass the test in D237022.
Pushed by krosylight@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/fedd4d89a0ea
Call NotifyFinished earlier for existing listener r=stransky
Comment 3•10 months ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 10 months ago
status-firefox137:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 137 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•