feat: add multi-tab state change notifications #566
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hf
requested review from
kangmingtay,
alaister and
J0
and removed request for
kangmingtay and
alaister
kangmingtay
approved these changes
Dec 23, 2022
|
So this should help resolve the issue where a |
This was referenced Dec 30, 2022
J0
approved these changes
Jan 4, 2023
hf
force-pushed
the
hf/add-multi-tab-notifications
branch
from
cabbc40 to
94d1e84
Compare
|
🎉 This PR is included in version 2.11.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uses the BroadcastChannel API to register a new broadcast channel (using the
storageKeyoption as the channel's name) which will broadcast state change events from the originating tab to all other open tabs.This is only available when a browser environment is detected and session persistence is enabled. Environments that are not browsers or browsers without session persistence are not able to use this feature since they have no way of synchronizing the underlying session storage.