Currently in gaia, if an app (SMS app for example) is launched after having send notifications we cannot automagically clear them from the notification tray. We could let the app manage this by exposing the (apparently spec'ed) .close() function on the notification object. If it can only be part of a larger rewrite of the DesktopNotificationAPI feel free to won't fix. [1] http://www.w3.org/TR/notifications/#api

Can't really make a blocking call until we know if this is WONTFIX or not.

Since it's possible to work around this in Gaia land, I would vote non-blocker, though I agree this is an important API point for DesktopNotifications

(In reply to Marshall Culpepper [:marshall_law] from comment #2) > Since it's possible to work around this in Gaia land, I would vote > non-blocker, though I agree this is an important API point for > DesktopNotifications What is the Gaia workaround you mentionned? The only way I could think is to delegate to the system application once bug 778668 has landed, is it what you have in mind?

Re-nominating until the Gaia workaround is explained.

If testing/dogfooding shows this is really bad on UX, we should re-consider nominating.

(In reply to Vivien Nicolas (:vingtetun) from comment #3) > What is the Gaia workaround you mentionned? It would have to be a Gaia-only workaround for now, i.e. expose a close() API (or similar) in Gaia's Notifications API, and Gaia apps could use this. This obviously wouldn't work for third party apps though :(

I would also add the ability to lock notification like on Android.