Yes, but the problem it is part of current standard, 2.0 is still work in progress. Also alternative API from SVG 2.0 is not yet delivered by Chrome either as far as I know.
The Chrome team removed something that there was agreement across all browsers to deprecate, and which was made optional in a near-finished spec.
Also, it's perfectly typical for drafts to be what implementers are targeting, as plenty of published specs receive almost no errata and any issues in them only get addressed in new revisions.
