Recently we have been hit by Chrome dropping API, which is part of SVG 1.1 specification. The reason: low usage and it is not part of the SVG 2.0 draft: https:&#x2F;&#x2F;code.google.com&#x2F;p&#x2F;chromium&#x2F;issues&#x2F;detail?id=553672 . Fortunately we test against Canary and as part of the quoted bug, a polyfill was provided, so we can live with that. But I&#x27;m really surprised firstly that part of current standard is just dropped, secondly that there was not a single warning in Chrome console saying we use some depreciated API. So this bring to the question:<p>How should the browser API depreciation look like?<p>I would expect there is at least some messaging around that. That there is some known upfront date, when it will stop working, at lest few months in advance, so that applications can adjust.<p>What are your thoughts?
Ask HN: How should browser API be dropped?