Remove "Prevent WebRTC from leaking local IP address" setting from uBO for Firefox for Android

[efk4]

Prerequisites

• I verified that this is not a filter list issue. Report any issues with filter lists or broken website functionality in the uAssets issue tracker.
• This is NOT a YouTube, Facebook or Twitch report. These sites MUST be reported by clicking their respective links.
• This is not a support issue or a question. For support, questions, or help, visit /r/uBlockOrigin.
• I performed a cursory search of the issue tracker to avoid opening a duplicate issue.
• The issue is not present after disabling uBO in the browser.
• I checked the documentation to understand that the issue I am reporting is not normal behavior.

I tried to reproduce the issue when...

• uBO is the only extension.
• uBO uses default lists and settings.
• using a new, unmodified browser profile.

Description

According to the uBO wiki (https://github.com/gorhill/uBlock/wiki/Dashboard:-Settings#prevent-webrtc-from-leaking-local-ip-address), the "Prevent WebRTC from leaking local IP address" setting still exists in Firefox for Android "because obfuscation is still not implemented." According to the issue linked from the wiki (https://bugzilla.mozilla.org/show_bug.cgi?id=1581947), Firefox has implemented obfuscation in pre-release builds and is targeting version 149 for stable release. Assuming that I have interpreted everything correctly, the "Prevent WebRTC from leaking local IP address" setting can now be removed from uBO for all browsers.

A specific URL where the issue occurs.

https://github.com/gorhill/uBlock/wiki/Dashboard:-Settings#prevent-webrtc-from-leaking-local-ip-address
https://bugzilla.mozilla.org/show_bug.cgi?id=1581947

Steps to Reproduce

The "Prevent WebRTC from leaking local IP address" setting is present in uBO for Firefox for Android because that browser did not support mDNS hostname obfuscation.

Expected behavior

Support for mDNS hostname obfuscation is planned for Firefox 149, so the "Prevent WebRTC from leaking local IP address" setting may be removed.

Troubleshooting information

uBlock Origin: 1.69.0
Firefox Mobile: 147
filterset (summary):
 network: 74569
 cosmetic: 41989
 scriptlet: 23177
 html: 3018
listset (total-discarded, last-updated):
 removed:
  user-filters: null
  ublock-badware: null
  ublock-privacy: null
  adguard-mobile: null
  easyprivacy: null
  urlhaus-1: null
  plowe-0: null
 default:
  ublock-filters: 44741-78, 20m Δ
  ublock-unbreak: 2794-1, 20m Δ
  ublock-quick-fixes: 456-13, 20m Δ
  easylist: 95006-127, 20m Δ
filterset (user): [empty]
switchRuleset:
 removed:
  no-csp-reports: * true
userSettings:
 hyperlinkAuditingDisabled: false
 prefetchingDisabled: false
 suspendUntilListsAreLoaded: false
hiddenSettings: [none]
supportStats:
 allReadyAfter: 13912 ms
 maxAssetCacheWait: 96 ms
 cacheBackend: indexedDB

[krystian3w]

I can confirm that the fix from bugzilla works in Firefox 149 Beta (downloaded from Google Play) with Android 15 (Tests from versions 8 to 11 of Android would be useful).

But other mobile forks can use Firefox 140 ESR (without mDNS masking) until the end of June before jumping to 153.

We can only hope that Waterfox will release its version on the 1.2.1+ "GeckoView" engine (including Gecko 149 branch/mDNS masking) in March (so they don't have to bother with manual merging (apart from other news from branch 149, staying longer on 148)).

[efk4]

But other mobile forks can use Firefox 140 ESR (without mDNS masking) until the end of June before jumping to 153.

Firefox ESR 140 will be supported until October 2026 (https://whattrainisitnow.com/release/?version=esr) and ESR 115 will be supported until at least March 2027 (https://support.mozilla.org/en-US/kb/firefox-users-windows-7-8-and-81-moving-extended-support). It may be necessary to keep this toggle until early next year.