Quote:
Originally Posted by Trubu
Chrome also autobuffers video like this - does it not autobuffer audio? Maybe they've changed that in more recent builds.
|
It might default to auto-buffering if the tags don't say anything about it, but Chrome respects the HTML5 tags when they tell it not to auto-buffer. Safari does not.
Quote:
|
While this is not an optimal behavior in your case, it doesn't actually disobey the draft spec:
|
It's just a draft. It's not that I'm accusing them of not satisfying the spec. I didn't say it was "wrongly implemented". I said it was poorly (atrociously?) implemented, and it is, for that kind of device. I fail to see what the point of the property is if the setting you choose makes no difference to how the browser handles it. In any case, my website locked up any iPad I used to try to open it. No website should have the ability to lock up the end-user's computer using nothing but HTML, and it's a poorly constructed browser if it allows it ever to happen. Of course, I wasn't trying to be malicious, but there are those out there that would be.
Quote:
|
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."
|
If you read the post I linked to, you'll see that I tried that. It just led to a different problem.
And just for fun:
