mdn-bcd-collector icon indicating copy to clipboard operation
mdn-bcd-collector copied to clipboard

Data collection service for MDN's browser-compat-data

Results 52 mdn-bcd-collector issues
Sort by recently updated
recently updated
newest added

See https://github.com/openwebdocs/mdn-bcd-collector/blob/18c9eb5bc2c7c6b45b7137f346c5eb08bda29be7/untestable-features.jsonc#L210C6-L210C97 "Worker support; technically already tested, but update-bcd doesn't know how to update these."

For some features, we are able to track spec URLs for features. CSS properties and values have spec URLs available on each feature, and IDL has some spec URL context...

https://github.com/mdn/browser-compat-data/issues/22288 mentions that there is no data for the `run-in` value of the `display` CSS property. In the [specification](https://drafts.csswg.org/css-display/#propdef-display), values are defined as types (ex. ``). Currently, we manually define...

I added state() manually to https://github.com/mdn/browser-compat-data/pull/22273 The collector should have detected it. Maybe it needs adding to https://github.com/openwebdocs/mdn-bcd-collector/blob/cda2aad87c254efe85d5583b31b8bf38bb80960d/custom/tests.yaml#L5554 https://developer.mozilla.org/en-US/docs/Web/CSS/:state https://html.spec.whatwg.org/multipage/semantics-other.html#selector-custom

This seems to have been introduced in the last update, most likely. If BCD has the version set to `null`, but the collector determines `false`, it does not appear to...

In https://github.com/openwebdocs/mdn-bcd-collector/pull/879 I re-enabled collecting compat data for events, but skipped those for global/window event handlers: ``` const skipIncludes = [ "WindowOrWorkerGlobalScope", // handled separately as globals "GlobalEventHandlers", // XXX...

There is a new gating mechanism for certain APIs. It's called "enrollment". I think it currently affects Google Chrome Desktop, Google Chrome Android and Google Android WebView. The following APIs...

As described in https://github.com/mdn/browser-compat-data/pull/21486 Chrome Desktop only shipped this API in v121. I can confirm this with manual testing. The collector tests need to be made better. Maybe it should...

I've been manually collecting results on beta browsers but ideally we want to collect results automatically. I think this PR should do that. This will help to reduce manual BCD...

Now that we are able to record data for problematic extensions, we should utilize it to remove results affected by those extensions.