Re: DIV in a page with Dynamic Web Template applied

From: Murray (forums_at_HAHAgreat-web-sights.com)
Date: 10/01/04 

Date: Fri, 1 Oct 2004 14:34:52 -0400

Xero:

Wanna tell me how you got that editable region around your body tag? 

-- 
Murray
"Xero" <jeff@chezjeff.(REMOVE)net> wrote in message 
news:37B9044C-9FFC-4ABD-AD48-50C7C4FE39A8@microsoft.com...
> Hello Murray,
>
> Thanks very much for reviewing my page ... I have managed to achieve who I
> what to do with the layers - when I want to work on a layer, I go to the 
> HTML
> view and place the cursor between the <div> tags. That is inconvenient but
> ... well, that's the only solution I can figure out.
>
> For the 'primary' layer ... please have a look at
> http://www.chezjeff.net/pages/winexplore.htm
>
> This page uses the code that I have posted in the last post. If you open 
> it
> in FrontPage, you will see that the image showing my site's logo (i.e. 
> this
> image : http://www.chezjeff.net/file_archives/logo_black_small.jpg), which 
> is
> made up of a Flash file and a JPG file, is placed in a layer (named as
> 'banner_lowerfragment) while the content of the page is placed on another
> (which is the 'primary' layer). The z-index of 'banner_lowerfragment' is
> lower than that of 'primary' so that the logo will appear beneath the 
> content
> of the page.
>
> "Murray" wrote:
>
>> That's pretty strange.
>>
>> I loaded your code, and there is nothing in the Layers panel.  I used 
>> FORMAT
>> | Dynamic Web Template > Detach from Dynamic Web Template, and the layers
>> appeared in the panel.  Then I just did an undo, and whaddya know?  The
>> layers stayed in the panel!  I dunno why!
>>
>> But, I have to tell you, I see at least two problems on that page.
>>
>> 1.  Much of your page content is wrapped in a layer called primary (I'm 
>> not
>> sure why you needed to do this), including the layer that you are wanting 
>> to
>> see in the editable region.  Nesting inline layers like this is going to
>> cause a rendering problem in some browsers (particularly NN4x).  If you 
>> want
>> to nest them (again, I am not sure what the need is for #primary, so I 
>> think
>> you could do without it), then you should make the inner layer (the one 
>> in
>> the editable region) be a fully qualified CSS layer (i.e., it contains no
>> inline styles, which have all been moved to the style***).
>>
>> 2.  That inner layer is in a table cell.  This is a much bigger problem.
>> You should never put absolutely positioned page elements (not necessarily
>> just divisions) directly into table cells, or you will have lots of
>> cross-browser/platform rendering problems.  Since absolutely positioned
>> elements are ... ermm ... absolutely positioned, they do not rely on 
>> tables
>> or any other page infrastructure for their placement on the screen.  This
>> being the case, their code can fall anywhere on the flow of code from 
>> <body>
>> to </body> without affecting that placement.
>>
>> In this case, however, you have a problem, since you are using DWTs and 
>> you
>> can only put things into editable regions.  The solution is to create a
>> special editable region right at the bottom of the page's code, e.g.,
>>
>> change -
>>
>> </body>
>>
>> to -
>>
>> <!-- #BeginEditable "layerPad" --><!-- #EndEditable -->
>> </body>
>>
>> and allow this change to propagate to the child pages.  Now, when you 
>> want
>> to insert a layer onto a child page, you just click inside this layerPad
>> region and use INSERT | Layer.
>>
>> Maybe that'll help you come to grips with this!
>>
>> -- 
>> Murray
>>
Loading