- From: Charles McCathieNevile <chaals@opera.com>
- Date: Thu, 26 Feb 2009 11:31:54 +0100
- To: "Sean Hogan" <shogun70@westnet.com.au>
- Cc: "Garrett Smith" <dhtmlkitchen@gmail.com>, "WebApps WG" <public-webapps@w3.org>
On Thu, 26 Feb 2009 04:49:47 +0100, Sean Hogan <shogun70@westnet.com.au>
wrote:
> Charles McCathieNevile wrote:
>> On Wed, 25 Feb 2009 22:59:06 +0100, Sean Hogan
>> <shogun70@westnet.com.au> wrote:
>>
>>> Garrett Smith wrote:
>>>> It might be worth discussing the load event;
>>>> http://www.w3.org/TR/DOM-Level-3-Events/events.html#event-load
>>>>
>>>> Seems that it is "specified" to fire on Document or Element (instead
>>>> of window).
>>>>
>>> I would also suggest a progress event on document or window.
>>> Ideally it would be triggered every 100ms during page-load.
>>
>> I would suggest that the editor of the progress spec get back to
>> dealing with the last issues raised by Ian, but he is writing this
>> email :)
> Sorry, I don't understand. Is the progress spec anticipated to augment
> DOM-3-Events for HTMLDocument and Window?
Well, Progress events are in a seperate spec if that is what you mean.
>> However the issue of timing is an interesting one...
>>
> The basis for the 100ms event interval is related to the rendering of
> new content on the web-page. If new content has arrived then scripts
> should be able to munge it before it is rendered, or at least soon
> afterwards. It doesn't matter how much content has arrived.
Is your use case for initial page loading (which I think is different from
when doing an XHR to get *more* data)? In that case I think it is more
reasonable to work at greater frequencies - although there is still the
question of how much you want to do...
>> When you emit an event it is pretty low cost. But when you deal with a
>> javascript that listens for that event and then does something else, it
>> is more expensive - and when that starts to eat the battery of your
>> mobile phone, maybe 10 times a second is more than people want.
>>
>> Anyway, I leave the issue of whether to request user agents to make a
>> particular timing available to the specs that use progress events,
>> although I have reservations about the wisdom of conditioning authors
>> to expect things just because broadband in a few countries can deliver
>> them easily.
>>
> I should raise this as a request for HTML5.
yep. I think it is actually in the spec already...
cheers
Chaals
--
Charles McCathieNevile Opera Software, Standards Group
je parle français -- hablo español -- jeg lærer norsk
http://my.opera.com/chaals Try Opera: http://www.opera.com
Received on Thursday, 26 February 2009 10:32:43 UTC