1786336 - Messaging Surface Triggers: Idle

Status: VERIFIED FIXED

(Firefox :: Messaging System, enhancement, P1)

Description

[lsmith]

As a team, we want to trigger messaging surfaces when in scenarios where users could be more efficiently using their bookmarks so that we can present relevant messaging surfaces to them and be contextual.

Comment 1

[Meg Viar [:mviar]]

Add a new message surface trigger and corresponding documentation that meets the following criteria:

• Idle is triggered after 20mins of inactivity
• If there are multiple windows/tabs open, the message will surface on the active tab
• If there is a video playing in the background, idle will not be triggered (P2)

Comment 2

[Shane Hughes [:aminomancer]]

Attachment: Bug 1786336 - Add idle message surface trigger. r=mviar

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/bd2a99189b8a
Add idle message surface trigger. r=mviar

Comment 4

[Atila Butkovits]

https://hg.mozilla.org/mozilla-central/rev/bd2a99189b8a

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

Since nightly and release are affected, beta will likely be affected too.
For more information, please visit auto_nag documentation.

Comment 6

[Shane Hughes [:aminomancer]]

Some more work on this incoming

Comment 7

[Shane Hughes [:aminomancer]]

Attachment: Bug 1786336 - Resolve some idle trigger issues. r=mviar

Comment 8

[Shane Hughes [:aminomancer]]

For reference, D161237 adds some new behavior to the idle trigger:

1. The idle trigger is completely disabled in permanent private browsing mode
2. If the user becomes active in a private window after an idle period, the trigger will not fire. Only resuming activity in a non-private window will fire this trigger. There isn't really a technical reason for this, it was just intended to avoid any perception that one's inputs are being unduly tracked in private windows.
3. If the user minimizes Firefox (or hides the window in some other way at the OS level), goes idle, then resumes activity without any Firefox window being visible, the trigger will not fire. Instead, the trigger will listen for Firefox windows to become visible. Once a window is visible, the trigger will fire (provided no sound is playing). Visibility changes will not normally fire the trigger though. They will only fire the trigger if an "active" notification was previously fired and "fizzled" due to every window being hidden.

Comment 9

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/f66d7cd78401
Resolve some idle trigger issues. r=mviar

Comment 10

[Ed Lee :Mardak]

(In reply to Shane Hughes [:aminomancer] from comment #6)

Some more work on this incoming

It's probably better to open a new bug for followups if it's already resolved fixed.

Comment 11

[Serban Stanca [:SerbanS]]

https://hg.mozilla.org/mozilla-central/rev/f66d7cd78401

Comment 12

[Carmen Fat [:cfat] - Ecosystem QA]

• I have verified the feature on Firefox Nightly 108.0a1 (Build ID: 20221109164728) and Beta 108.0b2 (Build ID: 20221115200658) on Windows 10 x64, macOS 12.6 and Ubuntu 20.04 x64.

• The targeted message is triggered after the computer is in an idle state for at least 1 minute (value set for testing purposes) and the user interacts with the pc (through keyboard or mouse).

• The message is not triggered if audio is played within the browser.

• The message is not triggered when Private Browsing Mode is enabled.

• The message is not triggered if Firefox is minimized and not visible on the Desktop. After Firefox is maximized and visible, the message is triggered and displayed.