[webkit-dev] SharedScript: next steps and result of offline discussion.
mjs at apple.com
Tue Dec 15 12:06:45 PST 2009
On Dec 15, 2009, at 11:09 AM, Michael Nordman wrote:
> On Mon, Dec 14, 2009 at 9:16 PM, Darin Fisher <darin at chromium.org>
> I think that use case has been de-emphasized. However, if we wanted
> to support it, we'd probably have to say that removeChild of an
> IFRAME element doesn't cause the unload event to be dispatched.
> (I'm a bit concerned that that may cause incompatibilities with
> existing pages.) Then, you'd have to store a reference to the
> IFRAME element in a global variable, so that you could find it again
> when the next document is loaded.
> I hope this use-case can be accommodated, I think this is ultimately
> the more generally applicable use-case. Btw, concern for
> incompatibilities with existing pages was one reason we came up with
> a new construct for this capability (instead of overloading <iframe>
> or <script>).
If you want to minimize new work on a page transition, then you should
use history.pushState and alter the content in place. Saving a subsite
of live script and DOM objects across a full page load does not seem
useful to me, since likely removing the full page load will be a
bigger improvement to load time and responsiveness.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev