Closed Bug 1789970 Opened 2 years ago Closed 1 year ago

Browser launches a separate instance every time the notifications are clicked

Categories

(Toolkit Graveyard :: Notifications and Alerts, defect)

Desktop
Windows
defect

Tracking

(firefox106 affected)

RESOLVED FIXED
Tracking Status
firefox106 --- affected

People

(Reporter: Gabi, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Attached video 2022-09-09_notif.mp4

Note

  • Have the messaging-system.rsexperimentloader.collection_id pref set to nimbus-preview
  • Have nimbus.debug set to true
  • Background update task is present in Task scheduler

Found in

  • Firefox Nightly 106.0a1

Affected versions

  • 106.0a1

Tested platforms

  • Affected platforms: Windows 10 x64, Windows 11x64
  • Unaffected platforms: macOS, Ubuntu - Windows 10/11 only feature

Steps to reproduce

  1. Install Nightly 106.0a1 on the default elevated profile
  2. Run the Background Update task inside the Task Scheduler
  3. Click X on the notification to move it to the action center
  4. Run the Background Update task to receive another notification
  5. Click to "Open Firefox now" on the toast notification
  6. Go to the action center and click the again on the notification

Expected result

  • Firefox Nightly is opened and notification is dismissed, no error message is displayed in the browser console

Actual result

  • Browser launches a separate instance every time the notifications are clicked
  • Notification error is seen in the browser console:

NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsITelemetry.getHistogramById] 3 TerminatorTelemetry.jsm:96
Error handling Windows notification with tag '0398610729': [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWindowsAlertsService.handleWindowsTag]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource:///modules/BrowserContentHandler.jsm :: dch_handle :: line 1051" data: no] BrowserContentHandler.jsm:1060
dch_handle resource:///modules/BrowserContentHandler.jsm:1060
Warning: unrecognized command line flag -profile
BrowserContentHandler.jsm:1144
dch_handle resource:///modules/BrowserContentHandler.jsm:1144

Regression range

  • New Feature

Additional notes

  • See the attached file
OS: Windows 10 → Windows
Summary: Browser is launched twice when clicking the native notifications → Browser launches a separate instance every time the notifications are clicked

:Gabi is this still the case or can we close this bug?

Flags: needinfo?(gasofie)

(In reply to Nick Rishel [:nrishel] from comment #1)

:Gabi is this still the case or can we close this bug?

I think we can go ahead and close it since we tested the notifications by enrolling into nimbus preview and the experiment was set for Firefox 106 users.

Flags: needinfo?(gasofie)
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: