Quote:
Originally Posted by frabjous
But in short: it prebuffers everything even if the HTML5 attributes tell it not to. Basically this means that if a page has multiple HTML5 tags it'll overwhelm the entire system. I've crashed many macs and iPads testing this. (The people at the store I did the testing at are starting to watch out for me now.) The MP3 codec used also plays many MP3s at the wrong frequency.
|
Chrome also autobuffers video like this - does it not autobuffer audio? Maybe they've changed that in more recent builds.
While this is not an optimal behavior in your case, it doesn't actually disobey the draft spec:
Quote:
|
The autobuffer attribute is a boolean attribute. Its presence hints to the user agent that the author believes that the media element will likely be used, even though the element does not have an autoplay attribute. (The attribute has no effect if used in conjunction with the autoplay attribute, though including both is not an error.) This attribute may be ignored altogether.
|
I can see why you were frustrated, though. FWIW, that behavior can
be worked around pretty easily with a JS onclick handler to swap in the tags "on demand."