Do you have a risk assessment and/or test plan for this feature? This feels like something that is both quite important and quite risky and I'd love to understand more about how you plan to test/validate this kind of feature.
--BDS On Thu, May 11, 2017 at 10:59 AM, Andreas Farre <fa...@mozilla.com> wrote: > Hi! > > As of 2017-05-15 I intend to turn on throttling of background tracking > timeouts by default. It has been developed behind the > dom.timeout.tracking_throttling_delay pref. Other relevant prefs are: > dom.min_tracking_timeout_value, > dom.min_tracking_background_timeout_value, > privacy.trackingprotection.annotate_channels. The values and relation > to background tracking timeout throttling of these prefs are: > > dom.timeout.tracking_throttling_delay pref: the pref that toggles the > feature, but also the amount of time that we wait before starting to > throttle background tracking timeouts after a document has finished > loading. A negative value indicates that the feature is turned off. > > dom.min_tracking_background_timeout_value: the minimum delay allowed > for a tracking timeout from a background window where more than > dom.timeout.tracking_throttling_delay pref ms has passed. > > dom.min_tracking_timeout_value: the minimum delay allowed for a > tracking timeout from a foreground window where more than > dom.timeout.tracking_throttling_delay pref ms has passed. > > privacy.trackingprotection.annotate_channels: if annotation of > channels based on the tracking protection list is turned on. Also > toggles this feature, needs to be true for this feature to be active. > > The feature is turned on by setting the following default prefs: > > dom.min_tracking_timeout_value: 4 > dom.min_tracking_background_timeout_value: 10000 > dom.timeout.tracking_throttling_delay: 30000 > > All values are in ms. This means that 30 seconds after a document has > finished loading, background tracking timeouts will run at most every > 10 second. > > Note that dom.min_tracking_timeout_value is a pref for throttling > tracking timeouts for foreground windows, but this is set to the same > value as dom.min_timeout_value, which is our minimum timeout delay for > regular foreground timeouts. That is, we do not currently treat > throttle tracking timeouts differently from other foreground timeouts. > > The bug tracking turning on this feature is: > https://bugzilla.mozilla.org/show_bug.cgi?id=1355311 > > This feature is similar, but not the same, as > https://trac.webkit.org/changeset/215116/webkit, where DOM timers are > throttled for all cross origin iframes. > > We would very much appreciate if we could get feedback on any issues > found while you're using nightly! > > Cheers, > Andreas > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
