- From: <bugzilla@jessica.w3.org>
- Date: Wed, 17 Aug 2011 18:04:20 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12595 --- Comment #8 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-17 18:04:19 UTC --- I think if we fire 'suspend' at the end, what's more likely to happen is that instead of just ignoring the event and having the element still mostly work, authors will wait for 'suspend' and treat it like 'onload', not starting to use the resource until it happens, and when it does, assuming the whole thing is cached. So for example they would load a sound effects file, wait for 'suspend', and then once it fires start playing back clips from anywhere in the file expecting zero latency. Why is this not worse? -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 17 August 2011 18:04:21 UTC