W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2009

[whatwg] <a onlyreplace>

From: Daniel Glazman <daniel.glazman@disruptive-innovations.com>
Date: Thu, 22 Oct 2009 16:47:37 +0200
Message-ID: <4AE07089.6000200@disruptive-innovations.com>
Tab Atkins Jr. wrote:

> I actually consider that a loss.  It's addressing a different problem,
> you see.  HTMLOverlays is basically client-side includes.  While you

It's client-side only because I implemented in JS that way! Explain
me what prevents from implementing server-side?


> I think you misunderstand the mechanics of @onlyreplace.  It doesn't
> change anything when you first load a page, and it shouldn't be at all
> similar to prefetching.  It only operates when you click on a link
> with the @onlyreplace attribute.  The browser then makes an ordinary
> request for the desired page, parses it with scripting disabled, and
> locates elements with the given ids to swap into the old page.

Exactly. And I said this is a good start and not enough. We could do
simple AND more powerful than that.

</Daniel>
Received on Thursday, 22 October 2009 07:47:37 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:18 UTC