- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Wed, 18 May 2011 07:17:56 +1200
On Wed, May 18, 2011 at 7:09 AM, Robert O'Callahan <robert at ocallahan.org>wrote:
> Sure! For certain kinds of events ("load", the video events, maybe more),
> delay the firing of such events until, say, after DOMContentLoaded has
> fired. If you're careful you might be able to make this a strict subset of
> the behaviors currently allowed by the spec ... i.e. you're pretending that
> your frame, image and video loads simply didn't complete until after
> DOMContentLoaded fired in the outer page. That would mean it's compatible
> with properly-written legacy content ... if there is any.
>
> Of course I have no idea whether that approach is actually feasible :-). It
> obviously isn't compatible with what browsers currently do, so authors
> wouldn't want to rely on it for a long time if ever.
>
However, given authors are already relying on this behavior, if it's
feasible it would probably improve app reliability and interop.
Rob
--
"Now the Bereans were of more noble character than the Thessalonians, for
they received the message with great eagerness and examined the Scriptures
every day to see if what Paul said was true." [Acts 17:11]
Received on Tuesday, 17 May 2011 12:17:56 UTC