bitwarden/browser
1
0
Fork 0
mirror of https://github.com/bitwarden/browser synced 2026-01-31 00:33:33 +00:00
Code Issues Releases Wiki Activity

Update libs/common/src/platform/server-notifications/README.md

Browse Source 
Co-authored-by: Derek Nance <dnance@bitwarden.com>
This commit is contained in:
Justin Baur
2025-12-10 11:40:39 -05:00
committed by GitHub
parent 676b212485
commit bc2e462acd
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
libs/common/src/platform/server-notifications/README.md
View File

@@ -81,7 +81,7 @@ That should largely have the same behavior and would allow us to maintain one fe
The foreground implementation is specially for browser foreground instances. At the moment this
service acts as a stub to avoid accidentally doubling up SignalR connections. If we had the default
implementation in both the background service worker and in each foreground instance anyone then
implementation in both the background service worker and in each foreground instance then there
would be a web socket connection made in each. With this special instance we avoid that by doing
nothing at the moment. Once we begin to fully support the `notifications$` observable we can make
a choice whether or not keep not supporting it in the browser foreground or we can decide to support