In certain circumstances, the WebRTC state will default to enabled but forced down the proxy, which is set per-tab. In some of those cases, I2P in Private Browsing, which displays a checkbox to reflect WebRTC enabled/disabled state, will show WebRTC as disabled when it is infact enabled. This doesn't seem to affect WebRTC obedience, so it doesn't introduce a vulnerability, but it does need to be corrected ASAP. Likely solution is to just check WebRTC state at a different point.
In certain circumstances, the WebRTC state will default to enabled but forced down the proxy, which is set per-tab. In some of those cases, I2P in Private Browsing, which displays a checkbox to reflect WebRTC enabled/disabled state, will show WebRTC as disabled when it is infact enabled. This doesn't seem to affect WebRTC obedience, so it doesn't introduce a vulnerability, but it does need to be corrected ASAP. Likely solution is to just check WebRTC state at a different point.