- From: <bugzilla@jessica.w3.org>
- Date: Wed, 04 May 2011 12:11:14 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12595 --- Comment #3 from Philip Jägenstedt <philipj@opera.com> 2011-05-04 12:11:13 UTC --- Some rationale for the change as well: 1. It's easier to implement if one fires the suspend event when the network stops being active, regardless of the reason. Specifically, it's annoying to have to special-case the situation when the last HTTP request (using Range header) happened to be the last piece to have the whole resource. 2. If one supports throwing away part of the cache, then having loaded all of the resource would in a sense just be suspending, because one might later have to resume buffering of evicted parts. 3. For page authors, it seems simpler to have a single event that always means that the network is no longer active. For example, a small indicated (glowing red sphere or some such) to indicate network activity would be easier to toggle on/off. The alternative is checking networkState in the progress event handler. -- 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, 4 May 2011 12:11:16 UTC