On Fri, Jul 7, 2017 at 5:57 PM, Ehsan Akhgari <ehsan.akhg...@gmail.com> wrote: > Yes indeed. (I just commented the same about unshipping another feature in > a different thread, so I won't repeat literally all of the same points here, > but they all apply here too!)
I created https://wiki.mozilla.org/WebAPI/ExposureGuidelines#Guidelines_for_removing_features so we have a place to point folks towards. Review appreciated. > FWIW I don't think we have ever included a version number (at least > according to my knowledge) and I don't think that is a good idea, since the > specific version number depends on the data and our guesses often end up > being wrong. But we usually don't consider these messages as "ultimatums", > rather we try to monitor usage and err on the side of not breaking content. A while back Blink changed how they handled this. They use the developer console to give a heads up when the telemetry gives very low numbers and they'd previously just remove it straight away. They basically do this for intranet deployments which likely would not have opted into telemetry and might therefore not have noticed yet still depend on such marginal features. And giving those folks a deadline helps them with planning. Also, they more or less stopped using the developer console to drive down usage. Not entirely sure about how I feel about this as I think it has been somewhat successful at times and for XMLHttpRequest it has resulted in less synchronous usage I think (though by far not enough to consider removing the functionality). On the other hand, too many warnings about "harmful" features and developers will start using a browser with a different console that's less spammy. -- https://annevankesteren.nl/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
