You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by mdedirudianto March 27, 2022
I tried new version of Quasar CLI BEX using manifest v3. It looks like that connection between content-script and dom has broken. Working fine with older version of Quasar webpack and BEX manifest v2. Please find my codes below to test
dom.js:
console.log('dom file')exportdefaultfunction(bridge){console.log('attach dom bridge')bridge.on('test',d=>{console.log('test from content',d.data)})console.log('send dom ready')bridge.send('dom-ready',{dom: true})}
my-content-script.js
console.log('content file')exportdefaultfunction(bridge){console.log('attach content')setInterval(async()=>{console.log('send test to dom');awaitbridge.send('test',{test: true});},5000);bridge.on('dom-ready',(event)=>{console.log('content dom-ready',event.data);})}
No message received on both side. Is there anything I missed?
The text was updated successfully, but these errors were encountered:
Discussed in #12947
Originally posted by mdedirudianto March 27, 2022
I tried new version of Quasar CLI BEX using manifest v3. It looks like that connection between content-script and dom has broken. Working fine with older version of Quasar webpack and BEX manifest v2. Please find my codes below to test
dom.js:
my-content-script.js
No message received on both side. Is there anything I missed?
The text was updated successfully, but these errors were encountered: