Your users simply need to provide the content page, which YOUR page (with
DWT attached) will display in the iFrame. They do NOT attach the DWT to
any of their pages.
The iFrame on YOUR page will be designed to show scrollbars as required by
the content pages. The iFrame should not be in an editable region, since
it does not need to be edited.
How the supplied content pages are navigated to is a different matter.
If you must have a page with a fixed length, consider using a scrollable
<div> for the content.
<div style="width:400px;height:300px;overflow:scroll;"><!-- #beginEditable
"UserContent" -->User content goes here<!-- #EndEditable --></div>
Also see inline below.
--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.
FrontPage Support:
http://www.frontpagemvps.com/
ATV said:
yes - confusion -
Let's start over. I was worried about being brief and concise.
I created the .dwt with an iframe as an editable region. In my .dwt I
set
the iframe to use a scroll bar if necessary.
OK
But beware the handicaps you are giving your website by using any sort of
frames.
Now what I want to happen is.... offsite creates a page of information
that
gets dropped into the iframe by attaching the page they write to the .dwt
and
placing it in the editable region.
Will not do what you want. The supplied content will REPLACE the iFrame,
not go into it.
What I thought would happen is their information would fill the iframe
and
the iframe would either add a scroll bar or not to keep the cells and
table
to the dimensions I set on the .dwt.
See above.
What is happening is if the info being attached to the .dwt in the iframe
is
too long... rather than adding the scroll bar... it is expanding the
cell.
Does that make sense?
Yes, perfect sense - that is what I would expect. The content is REPLACING
the iFrame, and taking up as much space as it needs.