The ignoreMissing mechanism is needed to capture constituent features that are not yet described in sources. That said, I note that this mechanism requires tracking spec updates: when new IDL or a new CSS property gets added to a spec, the list of constituent features will need to be updated.
Rather than being precise and tracking all changes in specs that are not yet stable, it may be useful to have a mechanism to say "this feature will likely have more constituent features". This could perhaps simply be done with the existing mechanism, e.g. listing "not.yet.specified" as query string.
Or perhaps it's fine and relatively easy to track spec updates, especially if this gets folded into BCD where this is already needed?
The
ignoreMissingmechanism is needed to capture constituent features that are not yet described in sources. That said, I note that this mechanism requires tracking spec updates: when new IDL or a new CSS property gets added to a spec, the list of constituent features will need to be updated.Rather than being precise and tracking all changes in specs that are not yet stable, it may be useful to have a mechanism to say "this feature will likely have more constituent features". This could perhaps simply be done with the existing mechanism, e.g. listing "not.yet.specified" as query string.
Or perhaps it's fine and relatively easy to track spec updates, especially if this gets folded into BCD where this is already needed?