Fix event handlers in broadcast message #245
Merged
+51
−21
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
|
esme
commented
Nov 20, 2024
esme
commented
Nov 20, 2024
alonso-cadenas
approved these changes
Nov 20, 2024
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.
Description
https://git.hubteam.com/HubSpot/calling-extensions-fe/issues/913
When receiving a broadcast message in the calling window, we need to invoke the event handler in
_ctirather thanctito send an SDK message to HubSpot.This is because the event handler, i.e. cti.initialized(), could technically send a broadcast message to the other tabs if iframeLocation has been set and we don't want to send another broadcast message when receiving one.
Merge Checklist
BRAVE Checklist