204719 2019-11-30 11:47:08 -0800 Unprefix AudioContext constructor? 2022-06-21 15:10:11 -0700 1 1 1 Unclassified WebKit Web Audio Safari Technology Preview Unspecified Unspecified RESOLVED DUPLICATE 216885 InRadar P2 Normal --- 1 timdream webkit-unassigned jer.noble philip puurtuur webkit-bug-importer oldest_to_newest 1594337 0 timdream 2019-11-30 11:47:08 -0800 I don't see anything on this tracker representing unprefixing the AudioContext constructor. Any specific reasons why it can't be unprefixed, given it was implemented since Safari 6? 1594338 1 webkit-bug-importer 2019-11-30 11:47:32 -0800 <rdar://problem/57540642> 1668206 2 philip 2020-07-02 03:14:49 -0700 It looks like WebKit is the only engine where AudioContext is still prefixed: https://developer.mozilla.org/en-US/docs/Web/API/AudioContext#Browser_compatibility (As webkitAudioContext) 1668208 3 philip 2020-07-02 03:17:41 -0700 Tests in WPT checking that the prefixed variant doesn't exist: https://wpt.fyi/results/webaudio/historical.html?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned 1668211 4 philip 2020-07-02 03:31:10 -0700 Hmm, it also looks like a lot of tests are failing or not run because of this. Example: https://wpt.fyi/results/webaudio/the-audio-api/the-audiobuffer-interface/audiobuffer.html?run_id=595470001&run_id=613910001&run_id=608350001 1877094 5 gsnedders 2022-06-21 15:10:11 -0700 Duping to where it got enabled. *** This bug has been marked as a duplicate of bug 216885 ***