W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 1998

Re: Frames and links

From: <nir.dagan@econ.upf.es>
Date: Fri, 18 Sep 1998 19:00:54 +0200
Message-Id: <H0000e2200b876b0@MHS>
TO: marja@w3.org
CC: w3c-wai-gl@w3.org
> Should we have a guideline for designers using frames to enable users to
> see the followed links and therefore be able to use back and forward
> buttons and bookmark the links? 

Yes. "Don't use frames" is a good guideline.

> To my knowledge the current techniques is having TARGET = "_top" in the
> FRAME links so that all the frames updated everytime a link is followed.

This kills the only advantage of frames: saving download time by having 
the navigation bar cached in the browser and replacing only the content 
page. Loading a new frameset involves of loading three documents (frameset 
+ at least two frames) every time someone follows a link.

> Maybe some less burdersome ways can be invented later.

There is one already. It is called CSS2 positioning properties.
You download one page when you follow a link and the cached 
stylesheet does all the multiple scrollbars stuff.
You can bookmark every page, and you can use the back and forward key 
without having any surprises. You can even print without problems,
as the frame-look is only suggested in the stylesheet for screen.

Nir Dagan
Received on Friday, 18 September 1998 12:51:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:33:27 UTC