Queen Vinyl Da.i'gyu-Kazotetsu

We don't actually handle event specifics like bubbling in the mdn-bcd-collector, so I can't really give any advice on this. As it is right now, the collector is only testing...

I did some digging into `IDBDatabase`, and wrote a comment on the related PR (#15006) stating why I think those subfeatures shouldn't have been removed -- hope that helps!

Looks like this needs to be formatted, could you run a formatter real quick to see what needs to be done to make this linter pass?

Note: the tests are failing because there are a lot of features that can be considered obsolete (or are not supported).

Hmm... It looks like the feature was originally set to "61", but was then set to "52" in https://github.com/mdn/browser-compat-data/pull/2858.

I'm in favor of `json_static` or `static_json` -- I don't expect this to happen too often and I feel that reworking the entire structure for it is not worthwhile.

Hey @gsnedders, looks like this PR may be awaiting your response!

We're actually using a slightly custom JSON stringification that is handled in `npm run fix`, so I don't think we should have two separate formatters running on the same files.

It looks like the interface is hidden behind a flag: https://searchfox.org/mozilla-central/source/dom/webidl/OffscreenCanvasRenderingContext2D.webidl#14 (running https://mdn-bcd-collector.appspot.com/tests/api/OffscreenCanvasRenderingContext2D in Firefox 104 shows no support) Running https://mdn-bcd-collector.appspot.com/tests/api/OffscreenCanvasRenderingContext2D/commit in all the latest browsers (Chrome 105, Firefox 104,...

#17880 was merged which sets this feature to "105". As a result, this flag data is now irrelevant and doesn't need to be added. I'm going to close this PR...