Closed argiopetech closed 7 years ago
The warning is normal given what uBO-Extra has to do, but I have checked with some other test cases found on the web that it did not cause an issue. I could reproduce the error, investigating.
I can't figure what is the issue, as my breakpoints are not triggered. For now I will create exceptions for some of the scriptlets, and I added hangouts.google.com
to the WebRTC wrapper.
Maybe add ipleak.net
too so that one can test if WebRTC would leak IP addresses to Google Hangouts?
ipleak.net
works fine for me, it could detect my local IP address when I disabled the setting in uBO.
That's true, sorry. I must have not disabled it when I tested.
Thanks for your quick resolution, @gorhill!
https://webrtc.github.io/samples
is also broken, seems to be the same issue, for example
https://webrtc.github.io/samples/src/content/peerconnection/webaudio-input
uBO extra 2.3
uBO extra 2.5
Can you confirmed above is fixed on your side with 2.6?
Yes https://webrtc.github.io/samples
is fixed with 2.6.
Not sure when this became an issue, but it's definitely present in 2.4. On attempting a call through https://hangouts.gooogle.com (just pressing "Video Call" button is sufficient), Chrome notes, "Error - Sorry, we encountered a problem joining this video call". The console shows:
This issue occurs only when uBO-Extra is enabled, never when it is disabled. The status of uBlock and uMatrix is irrelevant, i.e., uMatrix enabled with uBlock and uMatrix disabled still causes the issue to occur.