Claas Augner

Commit: https://github.com/mozilla/gecko-dev/commit/ae2e808431d115914d181650857e927eac819f7a Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=911987 (Firefox 51) PS: While we're there, we should use `alternative_name` here (as `prefix` technically gives `webkitonanimationend`): https://github.com/mdn/browser-compat-data/blob/538fabd90821e0d10e5c65fa9bbecf004aaec233/api/Element.json#L643-L646

> It's a bit unfortunate here, because http://example.com does not redirect to [example.com](https://example.com) :(. In those cases, how about using `http://developer.mozilla.org/`?

According to https://chromestatus.com/feature/5328467685801984, this only ships in Chrome Android, but neither [the implementing commit](https://github.com/chromium/chromium/commit/0ca582f08b2fa0b19af71f004f4155a3cada4573#diff-6a6a2cd009fc1bcd715b8791263830df02265591db8031c9cf130886b8a62900) nor [the shipping commit](https://chromiumdash.appspot.com/commit/5027847527f6da820842a5f2275fa9df6890bb7d) mention this restriction, so it probably ships in Desktop as well. @captainbrosset...

Thanks for clarifying. So what we need to do here is to mark `chrome` as partial implementation with notes (`Always returns 1. See [bug 419469463](https://issues.chromium.org/issues/419469463).`), and `chrome_android` as full support....

Closing as "won't fix", as we have mostly migrated away from ``.

> @zcorpan could you please work with @caugner on getting the Participation check resolved? @annevk This should be resolved now (thanks again @zcorpan). 🙂

> You need to make your membership of the organization public. Done, I was not aware. > Also please don't create merge commits in the future. Especially when they're not...

This looks like a duplicate of https://github.com/mdn/rari/issues/164. (Please let me know if you think this is a different issue.)

The BCD tables for both [ReadableStream](https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream#browser_compatibility) and [WritableStream](https://developer.mozilla.org/en-US/docs/Web/API/WritableStream#browser_compatibility) contain this information as "transferable" subfeatures (added in https://github.com/mdn/browser-compat-data/pull/16525), stating that Safari does not support this.

This looks like a Playground issue, because usually the images are copied from the corresponding content folder.