On Thu, Dec 13, 2012 at 10:11 PM, Anthony Jones <ajo...@mozilla.com> wrote: > Perhaps we could come up with an API > for exposing experimental features?
To go back to an earlier part of this thread: If you expose something on the release channel to Web authors, you are de facto releasing the feature for Web authors to bake into their sites/apps and risking it getting stuck in the sense that breaking changes cause a bad end user experience of sites/apps breaking. A moz prefix does not change that. Having to call enableExperimentalFeature() won’t change that. Writing documentation that says the feature is experimental won’t change that. > enableExperimentalFeature(feature, version) As with version suffixing, there is a very real risk that removing old versions will break too much content and so old versions stick around forever. In that case, the same kind of considerations as those stated in http://lists.w3.org/Archives/Public/public-html/2007Apr/0279.html and http://robert.ocallahan.org/2008/01/http-equiv_22.html apply. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
