BCD: Features that are also sub-features

MDN
#1

I’ve run into a strange situation with BCD data for Content Security Policy. The BCD for this includes 'report-sample' as a top-level feature. However, it’s actually a sub-feature of almost (but not quite) every CSP directive. As such, it ought to be listed in the compatibility tables for those directives.

Is there a way to create a compatibility table that includes both the data for a single feature (http.headers.csp.connect-src, for instance) and includes the data for another feature at the same time, such as http.headers.csp.report-sample (which is in fact the one I need to do)? Or do I need to duplicate the data for 'report-sample' across every directive that supports it?

1 Like
#2

BTW, the reason why 'report-sample' is being treated as a top-level feature of CSP is because it was added later, meaning that it may not be supported in all browsers, and theoretically may not be supported across all directives in all browsers.