Windows native notifications could have fail scenarios where they are not shown
Categories
(Toolkit :: Alerts Service, defect, P3)
Tracking
()
People
(Reporter: nrishel, Unassigned)
Details
When using native notifications with images, if an error occurs after saving the image the notification may not show. This is because the fallback-to-XUL logic is decided before the image is handled.
P4 - we are not aware of any remaining triggers of this problem, just that it's remains a fail scenario.
|
||
Comment 1•2 years ago
|
||
For the record, we might depend on not falling back to XUL in background tasks. I imagine the XUL fallback fails pretty quickly in background tasks but I've never investigated. If and when we make this more robust, we might want to avoid falling back in certain scenarios.
|
Reporter | |
Comment 2•2 years ago
•
|
||
I think we should consider disabling fallback altogether, there's no situation where it should be considered "correct" behavior and if triggered it would be hides a bug.
Edit: thinking more on this, I realize I'm only considering the Windows scenario, but the fallback logic is identical all platforms. "Disabling" it for Windows would essentially be returning "NS_OK" on errors.
|
||
Comment 3•2 years ago
|
||
This might make more sense under Core :: Widget: Win32, so feel free to move there instead.
Description
•