I agree, I opened an issue to address this: https://github.com/gorhill/uBlock/issues/773
Love the app, by the way. It's the single reason I have Firefox on my Android device instead of Chrome.
Do you happen to know WHY the leak breaks Hangouts? I'm assuming Hangouts now leverages the webRTC for connection--that's fine. But I was under the impression that the local IP leak was an unintended side-effect of webRTC, not a 'required component', if you will. Does having that checkbox on effectively break ALL webRTC components, or is it something specific with Hangouts' implementation?
Same here. My understanding is that the breakage of Hangout is unintended, as the original Chromium issue for the IP address leakage states[1]:
> This change causes WebRTC traffic to be forced through the same path that HTTP traffic would, i.e. the traffic follows the default route to the destination site.
In other words the purpose of the setting is strictly to prevent IP address leakage, not to prevent WebRTC from working.
[1] https://code.google.com/p/chromium/issues/detail?id=333752#c...
Edit: not sure why I'm getting downvoted. Apparently this is an issue, as gorhill mentions, when selecting the leaky IP option. They should make the implications much clearer.