search

mdn / sprints

Archived: MDN Web Docs issues are tracked in the content repository.
https://github.com/mdn/content
Creative Commons Zero v1.0 Universal
151 stars 144 forks source link

Update the linter to deal with missing BCD for completely unimplemented features #3970

Closed rachelandrew closed 3 years ago

rachelandrew commented 3 years ago

We have an issue in the CSS docs where some specs with broad implementation have a few properties unimplemented. If we don't document them there it's hard for developers to understand their status, however we don't want completely unimplemented properties in BCD even if in a stable spec.

Leaving no BCD means that the linter complains. I'd like to be able to have a way to indicate that there is no implementation, for example adding a line stating this where we would expect the BCD to go and have the linter understand this. It would help developers understand the status (and if it were a consistent bit of info would also mean we could search for these pages to check if any of them now have support)

re: https://github.com/mdn/browser-compat-data/pull/7511#issuecomment-744362920

chrisdavidmills commented 3 years ago

Issue moved to mdn/browser-compat-data #8790 via ZenHub