> I like the approach of disabling a feature (behind a pref) in non-Release (Beta and Nightly) for a few releases, to see what surfaces in bug reports.
This is reasonable, it is the approach we will be taking with the device sensors. Obviously it takes a little more work however I'm guessing the breakage risk will be higher than events . As you mention, I'm going to propose that we move to implement a pref to disable this feature instead. In Nightly and early beta enable this pref by default and see if we have any issues. Thanks Jonathan On Wed, Jan 3, 2018 at 7:49 PM, Mike Taylor <mi...@mozilla.com> wrote: > Hi Jonathan, > > > On Jan 3, 2018, at 9:15 AM, Jonathan Kingston <j...@mozilla.com> wrote: > > There is a small risk of breakage that we could decide to delay and > instead > > implement telemetry. However if the site is feature testing rather than > > user agent testing there shouldn't be an issue here. As this API throws > > errors there is likelihood websites account for it throwing anyway. I > would > > prefer however to let the removal ride the trains due to it's low risk > > before 61 so our ESR doesn't have it. > > I’m never confident sites are doing feature detection or handling errors… > I like the approach of disabling a feature (behind a pref) in non-Release > (Beta and Nightly) for a few releases, to see what surfaces in bug reports. > > > - Is only implemented by Firefox > > (It was also in Opera Presto 11.60+, RIP) > > -- > Mike Taylor > Web Compat, Mozilla > > > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
