Re: Intent to Ship throttling of tracking timeouts

[Eric Shepherd (Sheppy)]

Thank you for the details. I’ve added dev-doc-needed on the bug and added a 
link to this thread so the writer can find the information here quickly.

Eric Shepherd
Senior Technical Writer
Mozilla Developer Network 
Blog: https://www.bitstampede.com/
Twitter: https://twitter.com/sheppy

> On May 11, 2017, at 11:32 PM, Bill McCloskey  wrote:
> 
> (I hope everything I've said is correct. I've been following the change but
> I had nothing to do with the code.)

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Intent to Ship throttling of tracking timeouts

[Ehsan Akhgari]

On Thu, May 11, 2017 at 11:32 PM, Bill McCloskey 
wrote:

> On Thu, May 11, 2017 at 8:12 PM, Boris Zbarsky  wrote:
>
> > On 5/11/17 10:30 PM, Eric Shepherd (Sheppy) wrote:
> >
> >> So part of private browsing and not a developer-facing feature, then?
> >>
> >
> > No, as I understand this is being applied across the board, not just in
> > private browsing, and not just if tracking protection is generally
> enabled.
>
>
> Correct, this change will apply everywhere. Normally, when a script calls
> setTimeout, we enforce a minimum value on the timeout time. For foreground
> tabs this is 4ms and for background tabs it's 1000ms. The change being
> discussed will also factor in whether the script calling setTimeout is a
> tracking script (which is defined as a 

Re: Intent to Ship throttling of tracking timeouts

[Bill McCloskey]

On Thu, May 11, 2017 at 8:12 PM, Boris Zbarsky  wrote:

> On 5/11/17 10:30 PM, Eric Shepherd (Sheppy) wrote:
>
>> So part of private browsing and not a developer-facing feature, then?
>>
>
> No, as I understand this is being applied across the board, not just in
> private browsing, and not just if tracking protection is generally enabled.


Correct, this change will apply everywhere. Normally, when a script calls
setTimeout, we enforce a minimum value on the timeout time. For foreground
tabs this is 4ms and for background tabs it's 1000ms. The change being
discussed will also factor in whether the script calling setTimeout is a
tracking script (which is defined as a 

Re: Intent to Ship throttling of tracking timeouts

[Boris Zbarsky]

On 5/11/17 10:30 PM, Eric Shepherd (Sheppy) wrote:

So part of private browsing and not a developer-facing feature, then?


No, as I understand this is being applied across the board, not just in 
private browsing, and not just if tracking protection is generally enabled.


-Boris
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Intent to Ship throttling of tracking timeouts

[Eric Shepherd (Sheppy)]

So part of private browsing and not a developer-facing feature, then?

Eric Shepherd
Senior Technical Writer
Mozilla Developer Network 
Blog: https://www.bitstampede.com/
Twitter: https://twitter.com/sheppy

> On May 11, 2017, at 1:40 PM, Andreas Farre  wrote:
> 
> Timeouts classified using privacy.trackingprotection.annotate_channels as
> coming from a tracking script.

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Intent to Ship throttling of tracking timeouts

[Andreas Farre]

Timeouts classified using privacy.trackingprotection.annotate_channels as
coming from a tracking script.

On 11 May 2017 7:05 pm, "Boris Zbarsky"  wrote:

> On 5/11/17 10:59 AM, Andreas Farre wrote:
>
>> As of 2017-05-15 I intend to turn on throttling of background tracking
>> timeouts by default.
>>
>
> For purposes of this feature, what is the definition of "tracking timeout"?
>
> -Boris
> ___
> 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

Re: Intent to Ship throttling of tracking timeouts

[Boris Zbarsky]

On 5/11/17 10:59 AM, Andreas Farre wrote:

As of 2017-05-15 I intend to turn on throttling of background tracking
timeouts by default.


For purposes of this feature, what is the definition of "tracking timeout"?

-Boris
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Intent to Ship throttling of tracking timeouts

[Andreas Farre]

We've had help from QA testing this feature during the development,
and there is a test plan for the feature[1]. The delay before starting
throttling is something that was introduced to lower risk, and was
verified with the test plan.

We've also introduced telemetry measurements that we intend to use to
gauge the effectiveness of the throttling.

Cheers,
Andreas

[1] 
https://docs.google.com/document/d/1LYFso_NYoSIgP5qr1ivs7YR1udV34rHXQNJDpK_yiXU/edit?usp=sharing

On Thu, May 11, 2017 at 5:02 PM, Benjamin Smedberg
 wrote:
> 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  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: 1
>> dom.timeout.tracking_throttling_delay: 3
>>
>> 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

Re: Intent to Ship throttling of tracking timeouts

[Benjamin Smedberg]

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  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: 1
> dom.timeout.tracking_throttling_delay: 3
>
> 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

Intent to Ship throttling of tracking timeouts

[Andreas Farre]

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: 1
dom.timeout.tracking_throttling_delay: 3

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