When a stream is started by the content script, the tabId information in the endpoint data seems to get lost when it reaches the background script. Consequently, when attempting to send a message back to the content script using stream.send(), a TypeError is thrown.
I attempted a potential fix based on issue #66, which involved commenting out two specific lines of code. However, this resulted in an infinite loop in the aboutIncomingMessage function.
I'm not entirely familiar with the downstream logic, so any assistance in resolving this issue would be greatly appreciated.
Expected Behavior
stream.send() should send the message successfully
Version
6.0.1
Current Behavior
When a stream is started by the content script, the
tabId
information in the endpoint data seems to get lost when it reaches the background script. Consequently, when attempting to send a message back to the content script usingstream.send()
, a TypeError is thrown.I attempted a potential fix based on issue #66, which involved commenting out two specific lines of code. However, this resulted in an infinite loop in the
aboutIncomingMessage
function.I'm not entirely familiar with the downstream logic, so any assistance in resolving this issue would be greatly appreciated.
Expected Behavior
stream.send()
should send the message successfullySteps To Reproduce
Anything else?
No response