Re: Windows XP and Vista Long Term Support Plan

2016-10-31 Thread Robert Strong
Aaron, thank you for explaining the reasons for this decision so thoroughly! On Mon, Oct 31, 2016 at 3:48 PM, Aaron Klotz wrote: > Disclaimer: I am not a decision maker on this, these are my personal > opinions, etc, etc > > On 10/31/2016 3:54 PM, juar...@gmail.com wrote: >

Re: Windows XP and Vista Long Term Support Plan

2016-10-31 Thread juarezr
Em quinta-feira, 27 de outubro de 2016 11:48:13 UTC-2, Peter Dolanjski escreveu: > > > > What I think would be helpful if Mozilla does go with this plan, is that, > > first, Mozilla sets a definite end date up front for ESR 52 and, second, > > that Mozilla has puts out the message as to what and

Re: Intent to unship: navigator.getBattery (Battery Status API)

2016-10-31 Thread Chris Peterson
On 10/31/2016 11:23 AM, nicjan...@gmail.com wrote: Boomerang is an open-source library [1] for collecting performance telemetry. You're correct that it currently captures the battery level and other device characteristics. While Boomerang was not designed for the purpose of fingerprinting

Re: Intent to unship: navigator.getBattery (Battery Status API)

2016-10-31 Thread nicjansma
Boomerang is an open-source library [1] for collecting performance telemetry. You're correct that it currently captures the battery level and other device characteristics. While Boomerang was not designed for the purpose of fingerprinting users, it captures many performance metrics and page

Re: Removing navigator.buildID?

2016-10-31 Thread Domenic Denicola
On Monday, October 31, 2016 at 10:54:11 AM UTC-4, Mike Taylor wrote: > On 10/31/16 9:16 AM, Henri Sivonen wrote: > > On Oct 31, 2016 16:02, "Mike Taylor" > > wrote: > >> > >> > >> > >> On 10/29/16 9:21 AM, Kohei Yoshino wrote: > >>> > >>> I think now

Re: Removing navigator.buildID?

2016-10-31 Thread Mike Taylor
On 10/31/16 9:16 AM, Henri Sivonen wrote: On Oct 31, 2016 16:02, "Mike Taylor" > wrote: On 10/29/16 9:21 AM, Kohei Yoshino wrote: I think now is a good time to think about navigator.buildID again Thoughts? Seems like we'd potentially end up

Re: Removing navigator.buildID?

2016-10-31 Thread Henri Sivonen
On Oct 31, 2016 16:02, "Mike Taylor" wrote: > > > > On 10/29/16 9:21 AM, Kohei Yoshino wrote: >> >> I think now is a good time to think about navigator.buildID again >> Thoughts? > > > Seems like we'd potentially end up breaking legacy sites that sniff that to mean "isMozilla".

Re: Removing navigator.buildID?

2016-10-31 Thread Mike Taylor
On 10/29/16 9:21 AM, Kohei Yoshino wrote: I think now is a good time to think about navigator.buildID again Thoughts? Seems like we'd potentially end up breaking legacy sites that sniff that to mean "isMozilla". -- Mike Taylor Web Compat, Mozilla

Re: Removing navigator.buildID?

2016-10-31 Thread Henri Sivonen
On Mon, Oct 31, 2016 at 3:01 PM, Aryeh Gregor wrote: > On Mon, Oct 31, 2016 at 10:02 AM, Chris Peterson > wrote: >> Alternately, buildID could be hidden behind a domain whitelist pref, seeded >> with sites working with Mozilla. If you are, say, a Netflix

[desktop][mobile] Schedule Update for 50, ESR45.5 release and Merge day

2016-10-31 Thread Ritu Kothari
Schedule change: - 50 go-live date is Nov 15th (was Nov 8th). - ESR 45.5 go-live date is Nov 15th (was Nov 8th). - Merge day is Nov 14th (was Nov 7th). - Beta 51 cycle starts ~Nov 16th - Aurora 52 cycle starts ~Nov 18th. - Beta -> Release migration is Oct 31st (remains

Re: Removing navigator.buildID?

2016-10-31 Thread Aryeh Gregor
On Mon, Oct 31, 2016 at 10:02 AM, Chris Peterson wrote: > Alternately, buildID could be hidden behind a domain whitelist pref, seeded > with sites working with Mozilla. If you are, say, a Netflix customer, they > already know who you are, so exposing your buildID to them is

[Firefox Desktop] Issues found: October 24th to October 28th

2016-10-31 Thread Cornel Ionce
Hi everyone, Here's the list of new issues found and filed by the Desktop Release QA Team last week, *October 24**- October 28* (week 43). Additional details on the team's priorities last week, as well as the plans for the current week are available at:

Intent to unship: navigator.getBattery (Battery Status API)

2016-10-31 Thread Chris Peterson
As proposed earlier on the dev-platform list [1], I made the Battery Status API chrome-only in Firefox Nightly 52 (bug 1313580 [2]). The battery code and tests remain, available to Gecko code and Firefox add-ons. There should be little risk of web compat regressions. The battery API was never

Re: Removing navigator.buildID?

2016-10-31 Thread Chris Peterson
On 10/30/2016 2:27 AM, Pascal Chevrel wrote: IMO the builID is important for our community of nightly testers that report bug and need to indicate precisely in which build they found a regression, so keeping that information available via about:support and extensions such as Nightly Testers