Closed tomfa closed 1 year ago
The reference used to execute onMessage is the first reference of that function. I can only reproduce this with crossTab=true, and the bug only occurs in non-leader tabs.
A minimal reproducable example can be found here.
Note: you must open at least two tabs for the issue to be apparent, and it will not be present in leader tab
Version
A clear and concise description of what the bug is.
See codebox example here.
message()
Second tab should log updated counter value (3)
https://user-images.githubusercontent.com/1502702/216826601-fb1bb297-6457-410a-be98-7f104726bbbe.mov
OS
Device
Browser Vendor
This might be the culprit of the issues #289 and #293
Published as 5.3.3
5.3.3
Bug information
The reference used to execute onMessage is the first reference of that function. I can only reproduce this with crossTab=true, and the bug only occurs in non-leader tabs.
A minimal reproducable example can be found here.
Note: you must open at least two tabs for the issue to be apparent, and it will not be present in leader tab
Affected Module
Version
: Tested 5.5.2 and 5.3 – it happens in bothDescribe the bug
A clear and concise description of what the bug is.
To Reproduce
See codebox example here.
message()
Expected behavior
Second tab should log updated counter value (3)
Screenshots
https://user-images.githubusercontent.com/1502702/216826601-fb1bb297-6457-410a-be98-7f104726bbbe.mov
System Information (please complete the following information)
OS
: Mac OSX 12.0.1Device
: Macbook M1 ProBrowser Vendor
: ChromeAdditional context
This might be the culprit of the issues #289 and #293