Because Safari under Mac does not have this problem (OSX is installed by default), and the proportion of safari under Windows is really small.
Apple has stolen a little lazy. The so-called need for QuickTime is not to use QuickTime as a plugin, but the audio and video processing of Safari (including the entire MacOS) uses QuickTime as the backend.
This is different from plug-ins, Quicktimeframework is running as a system-level service under OSX, so-called QuickTime Player is just a client that invokes the service in the background, and Safari's audio is not "intrusive" A foreign module is attached to the browser, but Safari itself implements a background call to the QuickTime service. Kind of like a dynamic link
In fact, there are similar services in the Windows audio and video, IE is not to say that the direct internal implementation of the full audio and video playback function, but to call the system-level services to achieve. Now that Windows has preinstalled Windows player, does it have to be a lot of redundancy to implement a set in IE?
HTML5 audio is not valid in Safari (Windows)