Ehsan Akhgari schrieb:
I think we need to have a way to signal that we are not going to implement a specific feature in addition to those categories (without delving into the specific example here, but yes this is one of those features.) That sends a useful signal to other browser vendors and web developers. I know that for us, it would be hugely helpful to know if vendor X is actively planning to not implement a certain feature when weighing the pros and cons of working on something. I can imagine the same would be useful for other vendors, and it would be nice if we did that.
I agree, but I think we should have a wording that says something like "opposed to implementation" or similar and not "we will not implement", as we have seen in the past that things we didn't want to be implemented (that way) did actually pick up steam elsewhere and we ended up still implementing it - both for things that are not in line with our philosophy of the web, like EME, and for things where we had competing proposals (which we thought were the better way to go), like WebAudio.
KaiRo _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
