If a feature is usable but missing additional options, could we call the feature Baseline?

[kosamari]

(I was not sure where to post this question, please close this if it is not a fit for web-features repo)

I am looking at Conic Gradient which is available on cross browsers.
However, looking at MDN Browser compatibility table, Hue interpolation method and Interpolation color space are not yet supported on Firefox, this means the feature is usable but limited way to use them (than what is in spec).

In those case, could we call this a Baseline feature or should we wait until all implementation is complete with what is in speck??

[kosamari]

I run into same thing (partially missing support within bigger "feature") in color-scheme (https://developer.mozilla.org/en-US/docs/Web/CSS/color-scheme)

This feature is very much cross browser supported to support dark mode (which is the main use case, I assume) but still missing cross browser support for only light keyword.

[foolip]

In BCD we would either have a note on the feature, or add a subfeature for the missing parts which are not supported. For web-features, I think the choice is similar. If the feature is useful on its own, then define "conic gradient without hue interpolation or interpolation color space" as the main feature, and add subfeatures for the remaining parts.

Unlike BCD, I think we should also sunset subfeatures like that when they're far enough in the past.

There are no obvious answers here, these are just my initial thoughts. cc @ddbeck