Marking the above issue as Untriaged as this is a new feature request.

Thank you!

+Rebecca, Owen, Finnur, what do you think?

Developers can request this by setting the `requireInteraction` flag on a notification. When we move to use system notifications, at least for Windows and Mac, notifications will dismiss in their respective notification centers. This is already the case on Chrome OS.

I don't think that having an option is unreasonable, but we have a bit of an allergy towards settings. The easiest way to get this done is to have a global option in our (current) Content Settings display.

Implementing a command line flag to get this behaviour is trivial in either case.

It sort of sounds like this will be taken care of by introducing the notification center... no?

Mac is close-ish. Windows has no ETA and even when we ship it it'll likely be Windows 10+. That still leaves the vast majority of desktop users without options for the foreseeable future.

Yeah I try to avoid adding a setting for this and instead think of how to make the notification better first. Would we consider setting "requireInteraction" by default on notifications that a developer would have to turn off vs. turn on? Would that be TOO annoying? Or could we up the time the notification shows before dismissing? (Do we have metrics on how many notifications are going away without the user interacting?)

Could the Windows notification center be prioritized for Q4 or is Mac the testing ground before beginning work there?

I agree with Rebecca that we should avoid adding any new settings here but stick to our current plan of eventually moving things to the native notification centers.

I agree this is a mild pain point, but I think setting discoverability is already terrible so even if we introduced one, most users that would want it wouldn't discover it, so the bloat doesn't seem worth it, especially given we could put that eng time towards windows Notification Center (for our W10 users at least)

Okay, let's mark this as WontFix in favor of upcoming support for deferring to the system notification centers.

Changing the default value of `requireInteraction` is undesirable. It means we'd violate the specification (which can't default to TRUE for semantic reasons). It'd cause churn in behaviour we know is going to change in a near upcoming release again. It's _probably_ also not the preferred display for most notifications. We've received much less complaints about this than we expected.