To Frame or not?

[Travis Newbury]

Firstly, who wants to bookmark a page by examining its source code?
Secondly, if you bookmark a link within a frame and then visit that
bookmark, you get the contents of that frame on their own, and not in

the context of the frameset (AFAIK).

Well in some cases yes, but if the visitor is one of the 85% that have
javascript on you can easily check to see if it is in the frameset and
take the appropriate actions.

Mind you I am not advocating frames, just pointing out the gray. I
personally create web applications which don't have to follow the
rules. However our website is accessable to all (that speak English)
no scripting or anything else needed except if you are testing one of
the applications, and then you are told exaclty what you need to have.

 

[jake]

It is impossible, isn't it?
No.

Unless each page is actually a separate frameset.

But this completely defeats the "advantages" of using frames, namely
that you don't have to copy the same code into umpteen HTML files, and
don't have to re-transmit (and re-render) the non-changing frames in a
framset.

If you were an IE user you would know that you can simply click
'Favorites' 'Add to Favorites' and store the frames context with an
appropriate name in your chosen folder.

At some later date you can click on 'Favorites' , then the
bookmark-name. The frameset will be loaded, but with the frameset in
context as you originally saved it.

So. 90% of your viewers can bookmark frames 'in context'.

Other browser manufacturers haven't regarded this as a big-enough deal
to consider providing this option, although most (all?) modern browsers
allow you to bookmark individual frames.

And as long as a frame has a link back to the frameset, any 'orphaned'
pages located by search engines allow the user to get back to the
frameset page.regards.

 

[Oli Filth]

If you were an IE user you would know that you can simply click
'Favorites' 'Add to Favorites' and store the frames context with an
appropriate name in your chosen folder.

At some later date you can click on 'Favorites' , then the
bookmark-name. The frameset will be loaded, but with the frameset in
context as you originally saved it.

Ah, so you can! I'm not a user of frames, nor of IE (other than for
testing page rendering), so I never had any reason to know this

However, after playing around with this in IE, it's still not great.
Assume you add a particular location in the frameset at
http://example.com as a Favorite.

Now assume at a later date you visit http://example.com, and _then_
select that Favorite. Sure, the right page comes up, but if you now
click Back, it doesn't go back to the page in the frameset at
http://example.com that you were just on, but the page you were on
before you entered the frameset. Great.

However, maybe I'm missing something again!

 

[Toby Inkster]

However, after playing around with this in IE, it's still not great.
Assume you add a particular location in the frameset at
http://example.com as a Favorite.

Now assume at a later date you visit http://example.com, and _then_
select that Favorite. Sure, the right page comes up, but if you now
click Back, it doesn't go back to the page in the frameset at
http://example.com that you were just on, but the page you were on
before you entered the frameset. Great.

Errr.... that's the normal behaviour of bookmarks though.

 

[Oli Filth]

Oli Filth wrote:




Errr.... that's the normal behaviour of bookmarks though.

Que?

You're saying that if you're on a page at http://example.com, and you
click on a bookmark for another page at http://example.com, then click
Back, you'd expect it to jump back to the page you were on before you
entered http://example.com at all?

 

[Toby Inkster]

You're saying that if you're on a page at http://example.com, and you
click on a bookmark for another page at http://example.com, then click
Back, you'd expect it to jump back to the page you were on before you
entered http://example.com at all?

Ah, no. I must have misread.