On Tuesday 2015-06-30 17:00 -0400, Richard Barnes wrote: > Second, when we implement new web platform features, they will be enabled > only on secure contexts. Exceptions can be granted, but will need to be > justified as part of the Intent to Implement [3] and Intent to Ship process.
I think this needs to define what the granularity of a new feature is. Does it count new CSS properties that are closely related to existing ones? New values for existing CSS properties? Or by features are you talking only about doing things that the Web couldn't do before, rather than new built-in capabilities than make existing things easier or faster to do? Also, from a Web compatibility perspective, I don't think we can afford to do this for features that enough other browsers are shipping for all contexts. We implement some (though not too many) features because we're the last major browser to implement them; in those cases we're generally already dealing with a bunch of content that doesn't work in Firefox, especially on mobile, because of the lack of those features. -David -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla https://www.mozilla.org/ 𝄂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914)
signature.asc
Description: Digital signature
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
