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

[whatwg] framesets

From: Thomas Broyer <t.broyer@gmail.com>
Date: Mon, 12 Oct 2009 18:10:06 +0200
Message-ID: <a9699fd20910120910s4391353l5c3c497b1a17819f@mail.gmail.com>
On Mon, Oct 12, 2009 at 6:01 PM, Peter Brawley <pb at artfulsoftware.com> wrote:
> The use case that mainly motivates my objection to
> this says that the datatree maintenance page must function as a black box
> with no internal HTML bookmarking at all---except for exit, navigation must
> be controlled entirely by database/tree logic. The argument is not,
> therefore, that HTML5 should support new methods of bookmark blocking. The
> argument is that for this use case, which is best served by framesets till
> proved otherwise (and no-one has yet), the bookmark objection to framesets
> is invalid.

You have not proven why "this use case [...] is best served by
framesets" either. Actually, framesets alone don't answer your
requirement, you have to add:
 - a bit of JavaScript to use location.replace(...) in your links to
simulate a "single page application"
 - a bit of something to "block bookmarking" (user cannot use right
click -> open this frame in a new tab/window); unless we don't have
the same definition for "no internal HTML bookmarking"

I say that your use case is best served by AJAX (? la Google Document
Reader, just without the history trick using the location's hash).

-- 
Thomas Broyer
/t?.ma.b?wa.je/
Received on Monday, 12 October 2009 09:10:06 UTC

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