It might generate it anywhere
- but by putting it inside of the editable region at least you can remove it on pages
Put them inside of your Divs, just before your closing div tag
--
_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________
|
|
| "Stefan B Rusynko" wrote:
|
| > Caused by your comments
| > (where FP also inserts thr & <p> tags if thry are not in a container)
| > Try changing it to
| > <div id="intro"><!--intro-->
| > <div id="quicksummary"><!-- #BeginEditable "quicksummary" --><!--quicksummary--><!-- #EndEditable --></div>
| > <div id="preamble"><!-- #BeginEditable "preamble" --><!--preamble--><!-- #EndEditable --></div>
| > </div>
| >
| > --
| >
| > _____________________________________________
| > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > "Warning - Using the F1 Key will not break anything!" (-;
| > To find the best Newsgroup for FrontPage support see:
| >
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
| > _____________________________________________
| >
| >
| > |
| > |
| > | "Stefan B Rusynko" wrote:
| > |
| > | > The <p> tag is being added to the DWT when you save it
| > | > - open the DWT in browser and view source to see it
| > | >
| > | > Usually added because your editable region is
| > | > not is a valid html block level container
| > | > - like a <div> or <p> or <td) , etc
| > | > has an open html tag in it w/ no closing tag
| > | > or has a space after it
| > | >
| > | > Make sure the editable region is clean and has no extra spaces or line breaks after it as say
| > | >
| > | > <div>
| > | > <!-- #BeginEditable "content" --><p>some sample text</p><!-- #EndEditable -->
| > | > </div>
| > | >
| > | >
| > | > --
| > | >
| > | > _____________________________________________
| > | > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > | > "Warning - Using the F1 Key will not break anything!" (-;
| > | > To find the best Newsgroup for FrontPage support see:
| > | >
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
| > | > _____________________________________________
| > | >
| > | >
| > | > |
| > | > |
| > | > | "tcarp" wrote:
| > | > |
| > | > | > Working through my first major learning on CSS and the use of DWTs, I've
| > | > | > moved almost all of the basic structure of one of my sites to a DWT and
| > | > | > cleaned out almost all the formatting in the html and linked it to styles in
| > | > | > a CSS sheet. I'm now cleaning up the pages and have a couple editable
| > | > | > regions from the DWT that had an extra paragraph mark AFTER the region's
| > | > | > editable area. In other words, it looked that there was a <p> in the DWT in
| > | > | > the editable region but, when viewed from the actual web page it wasn't
| > | > | > inside the editable region (when I hovered over it I got the DO NOT ENTER
| > | > | > symbol). My assumption was that somehow there was a <p> in DWT but when I
| > | > | > went there to check: no <p>. So back to the code on the actual page and sure
| > | > | > enough there was an extra <p>nbsp; at the end of the region. The problem was
| > | > | > that is shows in the shaded area (i.e. implies that it's in the DWT).
| > | > | >
| > | > | > I can delete the extra html in the page but of course get warned that I'm
| > | > | > making changes in a non-editable area and am offered the choice of either
| > | > | > restoring the original code on save or accepting the changes. I accept the
| > | > | > changes and the code is wonderfully removed, but it looks like I'm going to
| > | > | > have to do this to each individual page that somehow has inherited the extra
| > | > | > code from somewhere.
| > | > | >
| > | > | > I did test to see if forcing a save of the DWT (thus updating each page it's
| > | > | > attached to) would clean things up (since the DWT actually is correct) but
| > | > | > the extra code remains.
| > | > | >
| > | > | > Does anyone know how this stuff got there so I can avoid it in the future
| > | > | > and is there a way, other than changing each actual page, to get the code
| > | > | > removed.
| > | > | >
| > | > | > Thanks
| > | > | >
| > | > | > Tom
| > | > |
| > | > |
| > | > | Addendum:
| > | > |
| > | > | I've done some further testing and found that the <p>nbsp; came back when
| > | > | the DWT associated with the page was resaved. Since the code isn't actually
| > | > | in the DWT but it shows up in the uneditable portion of the page it looks
| > | > | like FP is forcing the <p>nbsp; to be generated somehow.
| > | > |
| > | > | The bottom line is that deleting the code from the page (and forcing it to
| > | > | be accepted) gets overridden if the DWT is resaved.
| > | > |
| > | > | Tom
| > | >
| > | >
| > | > Hi Stephen
| > |
| > | Unfortunately, I don't think that's it. At least the DWT doesn't contain
| > | the <p>.
| > |
| > | This is the code from the DWT:
| > |
| > | <div id="intro">
| > | <div id="quicksummary">
| > | <!-- #BeginEditable "quicksummary" -->(quicksummary)<!--
| > | #EndEditable -->
| > | </div> <!--quicksummary-->
| > | <div id="preamble">
| > | <!-- #BeginEditable "preamble" -->(preamble)<!-- #EndEditable -->
| > | </div> <!--preamble-->
| > |
| > | </div> <!--intro-->
| > |
| > |
| > | As you can see there is no <p> in any of the <div>s here.
| > |
| > | This, however, is the code from the page that has the DWT attached (I've
| > | removed most of the text):
| > |
| > | <div id="intro">
| > | <div id="quicksummary">
| > | <!-- #BeginEditable "quicksummary" -->quicksummary text is
| > | here<!-- #EndEditable -->
| > | </div> <!--quicksummary-->
| > | <div id="preamble">
| > | <!-- #BeginEditable "preamble" --><p>Preamble text is here</p>
| > | <!-- #EndEditable --><p> </div> <!--preamble-->
| > |
| > | </div> <!--intro-->
| > |
| > | If you look at the <!--- #EndEditable --> you will see the <p> . In the
| > | page's code, this is "browned" out indicating that it is in the DWT (and in
| > | Design mode I get the do not enter when I hover over the paragraph mark).
| > | But, as you can see, no such code exists in the DWT.
| > |
| > | If I delete the <p> in the page's code and force it to be accepted, it
| > | disappears from the page but comes back the next time I make a change to the
| > | DWT.
| > |
| > |
| > |
| >
| >
| >
| Thanks again, Stephan
|
| Let me see if I got it. If there is a comment outside the editable region
| (in this case) FP might generate a <p>?
|
| I use comments next to closing </div>s to maintain my sanity a little. It
| helps me keep track of which DIV is being closed for nested DIVs. I usually
| put the comment after the closing </div>. If it were before that closing tag
| would FP NOT have generated the extra <p>?
|
| I may try a different approach to marking the ending <./div>s so that I can
| remove them altogether.
|
| And finally, your post implies that am I wrong in assuming that a comment is
| ignored by FP (or for that matter any other design tool). Is there a rule of
| thumb that I can use instead to understand when to avoid this issue?
|
| Thanks
|
| Tom
