I think that there would be many uses for a mechanism that allows
developers to take part in letting the UA known when it is "ready". For
example, we would use then when analyzing extension code server-side.
Another example would be systems that take screenshots of web pages for use
in browser start pages, or search results.
- a
On Mon, Apr 29, 2013 at 6:51 AM, Boris Zbarsky <bzbar...@mit.edu> wrote:
> On 4/29/13 6:50 AM, James Graham wrote:
>
>> So far we have kept the model where the load event is auomatically
>> managed by the UA, rather than giving the developer direct control of it.
>>
>
> Developers already have direct control over the load event to the extent
> being proposed, as far as I can tell. Consider this:
>
> var blockers = [];
> function blockOnload() {
> var i = document.createElement("**iframe");
> document.documentElement.**appendChild(i);
> blockers.push(i.**contentDocument);
> i.contentDocument.open();
> }
>
> function unblockOnload() {
> blockers.pop().close();
> }
>
> Of course expecting web developers to come up with this themselves and
> have to redo all this boilerplate is not reasonable, not to mention the
> pollutes-the-DOM and uses-way-too-much-memory aspect of it all.
>
> -Boris
>
