Is it possible to reproduce the issue without chase.com but with a small test case? The extension also works with jsfiddle so maybe you can share a live example like https://jsfiddle.net/3mrkqyea/?

That would make it much easier to investigate the issue.

I looked into this more closely. The issue is that bridge.js is being injected into the page as a <script> tag so all top-level functions defined in bridge.js will be defined on window. So the dispatchEvent function defined in bridge.js is overwriting the native window.dispatchEvent which interferes with any webpage that wants to use window.dispatchEvent. You can verify this is the case by logging window.dispatchEvent to console -- you get the function source from bridge.js instead of ƒ dispatchEvent() { [native code] }

You can see the issue here: https://jsfiddle.net/xe74sado/1/

I suspect the fix is to wrap bridge.js in an anonymous function so that nothing is defined on window. It's late, I can look into that tomorrow.

I suspect the fix is to wrap bridge.js in an anonymous function so that nothing is defined on window. It's late, I can look into that tomorrow.

Would be great if you can take a look 🙏