> How do you measure the behavior? AIUI those four prefs determine the behavior. They are set by default, but a user can create them. Because they aren't set by default the provided default values [where they are used](https://searchfox.org/mozilla-central/rev/e22715d304f4dcf18c58667b7db3535cfd828f24/dom/html/HTMLMediaElement.cpp#3133-3152) are used instead. If the `preload` attribute is not set in HTML then GetPreloadDefault() is used; and if it is set _and_ it is set to `auto` then it will use GetPreloadDefaultAuto(). On Android, the only place we check if you're on cellular, you could distinguish between Cellular or WiFi connection. I think the fix is on [these two lines](https://searchfox.org/mozilla-central/rev/e22715d304f4dcf18c58667b7db3535cfd828f24/dom/html/HTMLMediaElement.cpp#3137,3146) to do > if (OnCellularConnection() && !ShouldREsistFingerprinting(RFPTarget::MediaPreloadConnectionLink) { which will go use [this member function](https://searchfox.org/mozilla-central/rev/e22715d304f4dcf18c58667b7db3535cfd828f24/dom/html/HTMLMediaElement.cpp#6607-6609). That RFPTarget doesn't exist, it would [be added here](https://searchfox.org/mozilla-central/source/toolkit/components/resistfingerprinting/RFPTargets.inc). I think that will control both the loading behavior and the value reported for the default value of the preload attribute.
Bug 1969210 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> How do you measure the behavior? AIUI those four prefs determine the behavior. They are set not by default, but a user can create them. Because they aren't set by default the provided default values [where they are used](https://searchfox.org/mozilla-central/rev/e22715d304f4dcf18c58667b7db3535cfd828f24/dom/html/HTMLMediaElement.cpp#3133-3152) are used instead. If the `preload` attribute is not set in HTML then GetPreloadDefault() is used; and if it is set _and_ it is set to `auto` then it will use GetPreloadDefaultAuto(). On Android, the only place we check if you're on cellular, you could distinguish between Cellular or WiFi connection. I think the fix is on [these two lines](https://searchfox.org/mozilla-central/rev/e22715d304f4dcf18c58667b7db3535cfd828f24/dom/html/HTMLMediaElement.cpp#3137,3146) to do > if (OnCellularConnection() && !ShouldREsistFingerprinting(RFPTarget::MediaPreloadConnectionLink) { which will go use [this member function](https://searchfox.org/mozilla-central/rev/e22715d304f4dcf18c58667b7db3535cfd828f24/dom/html/HTMLMediaElement.cpp#6607-6609). That RFPTarget doesn't exist, it would [be added here](https://searchfox.org/mozilla-central/source/toolkit/components/resistfingerprinting/RFPTargets.inc). I think that will control both the loading behavior and the value reported for the default value of the preload attribute.
> How do you measure the behavior? AIUI those four prefs determine the behavior. They are set not by default, but a user can create them. Because they aren't set by default the provided default values [where they are used](https://searchfox.org/mozilla-central/rev/e22715d304f4dcf18c58667b7db3535cfd828f24/dom/html/HTMLMediaElement.cpp#3133-3152) are used instead. If the `preload` attribute is not set in HTML then GetPreloadDefault() is used; and if it is set _and_ it is set to `auto` then it will use GetPreloadDefaultAuto(). On Android, the only place we check if you're on cellular, you could distinguish between Cellular or WiFi connection. I think the fix is on [these two lines](https://searchfox.org/mozilla-central/rev/e22715d304f4dcf18c58667b7db3535cfd828f24/dom/html/HTMLMediaElement.cpp#3137,3146) to do > if (OnCellularConnection() && !ShouldResistFingerprinting(RFPTarget::MediaPreloadConnectionLink) { which will go use [this member function](https://searchfox.org/mozilla-central/rev/e22715d304f4dcf18c58667b7db3535cfd828f24/dom/html/HTMLMediaElement.cpp#6607-6609). That RFPTarget doesn't exist, it would [be added here](https://searchfox.org/mozilla-central/source/toolkit/components/resistfingerprinting/RFPTargets.inc). I think that will control both the loading behavior and the value reported for the default value of the preload attribute. It will also mean that RFP users will use _more_ bandwidth preloading things on cellular connections. Tor can voice their opinion, but from a user experience POV the added bandwidth will mean a Tor user will see the media _much faster_ because of the Tor network's added latency.