- From: Marcos Caceres <m.caceres@qut.edu.au>
- Date: Wed, 15 Nov 2006 10:18:04 +1000
- To: public-appformats@w3.org
Hi, Just wondering, does anyone else think that the behavior of the <prefetch> element is slightly underspecified? The spec provides limited answers to the following questions: Do prefetched resources load synchronously or asynchronously? (it is implied that it is asynchronous, but it doesn't say) While preloading, do these elements block the document's onLoad event until they have loaded? Once the element actually starts loading, should it fire an event on the implementation? Once an element has loaded, should it fire an event on the implementation? If the element fails to load, should it fire an event on the implementation? If the src attribute points to an invalid url, does the UA fire an event? or is it in error and ignored? If the author finds the prefetch taking too long, how can they cancel it? (Ie, should there be a scripting interface?) What happens when the MIME type of the prefetched resource is unknown to the User Agent? for instance, the author prefetches 'foo.fum' of type 'application/apples' Can I access the internals of the data I have preloaded from the prefetch element? say, for instance, I load some RSS and I want to parse it? (ie. why use prefetch instead of XHR or just javascript?) What's the scope of prefetch? can prefetched resources, like images for example, be used by a bound document? (implied no, but does not say) Regards, Marcos
Received on Wednesday, 15 November 2006 00:18:24 UTC