On 7/27/17 2:02 AM, Michael Kriegel wrote:
4. At a fixed date (e.g. 24 Months after X) all browsers must stop
supporting the feature
How do you plan to enforce this?
Please note that the people representing browsers in this committee may
not (and afaict generally do not) make ship/no-ship product decisions
for their browsers, so the can't even credibly commit to what you suggest.
Authors of Websites, for which there is still interest, will update
their code. Other websites will just break and nobody will care.
Unfortunately, you're wrong. That's because interest is asymmetric:
_users_ may have interest in a site even if the _author_ does not. So
it's quite possible (and in fact has happened before) that sites will
not be updated, they will break, and users will in fact care.
This happens all the time, even with well-advertised multi-year
deprecations, well publicized cutoff times and large companies that have
the resources to update their sites if they want to. See the story of
Google Hangouts, for example.
So I do not see a risk of "breaking the web" when there is such a clear
plan set up. There would be just the question how browser vendors could
be punished, if they do not comply and try to get an advantage over
other browsers by continuing support of those old features...?
Good luck with that.
-Boris
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
