Re: Targeting to <DIV> (or other ids)

Jordan Reiter (
Wed, 26 Nov 1997 12:07:20 -0500

Date: Wed, 26 Nov 1997 12:07:20 -0500
Message-Id: <l03110702b0a1c20d1e86@[]>
In-Reply-To: <>
To: Andrew n marshall <>
From: Jordan Reiter <>
Cc: "''" <>
Subject: Re: Targeting to <DIV> (or other ids)

=7FAndrew n marshall felt an urge to reveal at 11:18 PM -0800 on 11/25/97:

> Something that I just realized, thanks to my "<DIV> as Frames" example:
> With CSS-2's overflow:scroll there should be a way to scroll to a
> particular section of the enclosed content.  In frames, this would be done
> with the 'TARGET=3D'.  Currently this refers to Frame names.  I recommend =
> extend this to include id's by preceding the value by a '#'.  For example:
> <DIV id=3D'sidebar'>
>    <A href=3D'#sect2' target=3D'#main'>Section 2</A>
> </DIV>
> <DIV id=3D'main'>
>    . . .
>    <DIV id=3D'sect2'>
>       <H1>Section Two</H2>
>       . . .
>    </DIV>
> </DIV>
> The bigger question this brings to mind is: Does this allow embedding
> documents?  Personally, I don't like the idea of embedding documents over
> arbitrary elements.  Anyone have any other suggestions to get around this?

I think this doesn't. Because think about it--essentially it's telling the
page to jump to that section of text, no different than in a standard
non-CSS page. The browser should simply jump to that text, and if it means
scrolling a floating element, so be it. But it doesn't imply that documents
can be embedded in the DIV element, it just means that it appears to be
that way. This in fact has perfect degredation, btw, to lower browsers that
normally would be looking at a blank screen (no frames).

[           Jordan Reiter                             ]
[                ]
[  "It's well known that dead people are all sick     ]
[   because they're too depressing."                  ]
[   -- from ]