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

[whatwg] <a onlyreplace>

From: Nelson Menezes <flying.mushroom@gmail.com>
Date: Tue, 20 Oct 2009 13:22:15 +0200
Message-ID: <a440ea080910200422q4a08aa09lb93d314d0acbafab@mail.gmail.com>
2009/10/19 Schuyler Duveen <whatwg at graffitiweb.org>:
> I'm starting to think the addressability is the main constraint. ?What
> if the original @onlyreplace anchor tag:
>
> ? <a onlyreplace="id1 id2" href="page2.html" />
>
> would be equivalent to something like this:
>
> ? <a href="#view(page2.html id1 id2)" />
>
> which would process onload or onhashchange as we've been describing
> @onlyreplace and would appear in the browser's location bar. ?A more
> complicated one (after two jumps) might look something like:
>
> http://example.com/page1.html#view(page2.html id1 id2);view(page3 id3)

Then you are putting specific functionality in the hash. And you would
have to, to allow bookmarking. But this breaks the semantics of
linking, whereby the hash corresponds to a place within the page
(which AJAX applications sometimes use to reconstruct some sort of
state). What you are suggesting is putting this AJAX pattern in the
browser, in a specific format.

I'm not keen on solving this problem by changing the way linking
works; that was the beauty of the original proposal (other problems
notwithstanding). This seems like a fancy way to bookmark frames...


Nelson Menezes
http://fittopage.org
Received on Tuesday, 20 October 2009 04:22:15 UTC

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