1737852 - Support the NetworkInformation effectiveType property for webcompat

Status: RESOLVED INVALID

(Core :: DOM: Core & HTML, enhancement, P3)

Description

[Thomas Wisniewski [:twisniewski]]

It turns out that Chanel's mobile website is relying on navigator.connection.effectiveType without falling back on the type property, causing entire pages to break and not render at all. So not supporting effectiveType may be a webcompat issue now.

Comment 1

[Karl Dubost💡 :karlcow]

This is now very dependent on Bug 1637922 where we fully deactivated navigator.connection on Android.
Regression are being tracked at Bug 1755852

Comment 2

[Karl Dubost💡 :karlcow]

Note that it was shimmed.
https://github.com/mozilla-mobile/android-components/blob/055e202ce6a282724177952c419a99c6add5b808/components/feature/webcompat/src/main/assets/extensions/webcompat/injections/js/bug1751065-chanel.com-effectiveType-shim.js

Comment 3

[Simon Mainey]

Note that privacy.resistFingerprinting (when dom.netinfo.enabled is true) protects type (it returns unknown - see Bug 1372072 ). When/if this goes ahead, we should think about what to do with effectiveType as well

Comment 4

[Tom Ritter [:tjr] (OOTO until 4/30 at least)]

Seeing as we just disabled the other API we're probably okay here; but yes if we do ever re-enable the API and implement this, we should make sure it respects RFP.

Comment 5

[Karl Dubost💡 :karlcow]

The shim is not useful anymore. The chanel site has changed.