Re: Intent to Ship throttling of tracking timeouts

2017-05-12 Thread 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:/

Re: Intent to Ship throttling of tracking timeouts

2017-05-11 Thread 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 a

Re: Intent to Ship throttling of tracking timeouts

2017-05-11 Thread 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

Re: Intent to Ship throttling of tracking timeouts

2017-05-11 Thread 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

Re: Intent to Ship throttling of tracking timeouts

2017-05-11 Thread 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: > > T

Re: Intent to Ship throttling of tracking timeouts

2017-05-11 Thread 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.

Re: Intent to Ship throttling of tracking timeouts

2017-05-11 Thread 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

Re: Intent to Ship throttling of tracking timeouts

2017-05-11 Thread 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

Re: Intent to Ship throttling of tracking timeouts

2017-05-11 Thread 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! >

Intent to Ship throttling of tracking timeouts

2017-05-11 Thread 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.trackingprotect