Event data is wrong due to interface object not being exposed originally

[foolip]

The data in https://github.com/mdn/browser-compat-data/pull/11791 is likely wrong for the reasons outlined in https://github.com/mdn/browser-compat-data/pull/11881#issuecomment-896595350.

https://trac.webkit.org/changeset/94493/webkit added window.CompositionEvent and that happened in Chrome 15, but instances of the event interface were probably supported before that.

cc @vinyldarkscratch

[foolip]

Actually here's a checklist for all of the potentially affected events based on the patch:

• [x] AudioProcessingEvent (Chrome 14 + Safari 6, but that matches ScriptProcessorNode)
• [x] CompositionEvent (matches composition events on Element)
• [x] ErrorEvent (Safari true, check again once filled in)
• [x] MediaStreamEvent (Chrome true, check again once filled in)
• [ ] OfflineAudioCompletionEvent (doesn't match OfflineAudioContext, needs fixing)
• [x] PopStateEvent (Safari true, check again once filled in)
• [x] SpeechInputEvent (not in BCD)
• [x] WebGLContextEvent (Chrome 9 + Safari 5.1)
• [x] XMLHttpRequestProgressEvent (not in BCD)

Any of these that have Chrome 15 or Safari 6 as the version anywhere should be vetted.

[foolip]

Based on this I think CompositionEvent was introduced in Chrome 4 or later: https://trac.webkit.org/changeset/50968/webkit https://trac.webkit.org/browser/webkit/trunk/WebCore/Configurations/Version.xcconfig?rev=50968

But I'm not confident if it's Chrome 4 or 5, so some kind of testing is needed.