U - Fix CSS linter errors: data.browser_compatibility errors

[wbamberg]

The linter will check that pages correctly include this ingredient.

As per the spec for the linter, there are two specific errors that the linter raises here.

• "data.browser_compatibility/expected-heading" is raised when the page doesn't have an H2 "Browser compatibility".
• "data.browser_compatibility/expected-macro" is raised when the section does not include a call to the {{Compat}} macro.

Currently we have 42 "data.browser_compatibility/expected-heading" errors and 46 "data.browser_compatibility/expected-macro" errors. They are listed in the spreadsheet, all together in the "data.browser_compatibility" tab.

A substantial number of these will involve adding the BCD for these features.

Acceptance criteria

• There are zero errors reported by the linter for the "data.browser_compatibility" ingredient, when run against https://developer.mozilla.org/en-US/docs/Web/CSS

[rachelandrew]

This one has a lot of entries which seem to be fine so I'm not sure what to do with them. For example: https://wiki.developer.mozilla.org/en-US/docs/Web/CSS/place-self and other alignment properties.

There are some which have no BCD due to having no support yet. I could make a BCD showing no support? I guess that is useful to show people who might try and use it, what do you think @ddbeck

[rachelandrew]

I wonder if things like https://wiki.developer.mozilla.org/en-US/docs/Web/CSS/justify-content#Browser_compatibility are getting caught by the linter because they have a subheading?

[rachelandrew]

@ddbeck @chrisdavidmills this page https://wiki.developer.mozilla.org/en-US/docs/Web/CSS/filter-function is about the function as a value. Does it need it's own compat or would showing compat for the filter property which uses it be the thing to do?

[rachelandrew]

I have also noted in the spreadsheet the ones I have checked but which seem to have a heading and call to compat so I don't know why they are being flagged up.