I'd like to remove the un-used DOMImplementationHasFeature and DOMImplementationHasFeatureReturnsFalse UseCounter enums, and you might be able to use the enum values for the new enums you'll add for requiredFeature. You should check the procedure for removing UseCounter enums before going ahead with my suggestion.
Those enum values are already gone from UseCounter.h, but in any case you should normally not reuse entries, just add a new one.
But in this case, this is covered by a use counter with low usage, so I wouldn't bother trying to split it further:
https://www.chromestatus.com/metrics/feature/timeline/popularity/1072
You should probably also investigate if requiredExtensions and systemLanguage really make sense, or if they could be removed too, which would require a spec change.
Conclusion on https://github.com/w3c/svgwg/issues/308 was to keep it out of the spec. Whether or not that's the right call, this will now need some action on our part to move forward.
#14, if you want to assign this to yourself and drive the deprecation/removal, that'd be great. The next step would be to send an Intent to Deprecate and Remove to blink-dev. requiredFeatures doesn't do anything, and usage is bounded by https://www.chromestatus.com/metrics/feature/timeline/popularity/1072
One milestone of deprecation seems like a good idea, but no need for two separate intents for the deprecation and removal.
Comment#4: asked to remove DOMImplementationHasFeature also.
WIP CL: https://codereview.chromium.org/2787853002/
A lot of tests were failing, and need to be removed.
If we don't include C#4 in this bucket of work, then its fixed and i can land the WIP CL separately sometime later.
I don't think we should be doing that, see https://codereview.chromium.org/1108293002 for additional context. (Also, note that the use-counter was removed by that CL...)
Comment 1 by shanmug...@samsung.com
, Aug 8 2016