On 07/07/2017 03:41 AM, Anne van Kesteren wrote:
On Fri, Jul 7, 2017 at 8:51 AM, Jet Villegas <jville...@mozilla.com> wrote:
Depending on what you find, we may have to keep this API around :-/
Yeah, I would expect us to follow the "normal" deprecation and remove
path to be more confident in the eventual unshipping:
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!)
1. Gather telemetry on how often these APIs are used to measure feasibility.
2. Indicate in the console when these APIs are used that they are deprecated.
3. Bonus points for indicating in the console by which Firefox release
they are expected to be gone. (This might require more knowledge on
usage though.)
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.
(Perhaps this is not documented anywhere currently?)
To the best of my knowledge, it isn't documented anywhere besides the
archives of this list. :-/
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
