The following HTML text is output for a content profile display:

<p id="content-profile-view"><span id="thmr_5" class="thmr_call">
  <span id="thmr_4" class="thmr_call">
  <div class="content-profile-display">
(snip)
<div class="content">
    <div class="profile_text"><p>XXXXX is a Consultant and has 18 years experience in the Information Technology industry 12 with XXXXXX.<br />
XXXXX has use many technologies and paradigms over that time and his current passions are for:
<ul>
<li>OO design</li>
<li>Developing Infrastructure to reduce development effort</li>

<li>simplifying development</li>
<li>Using only standards within Java applications</li>
</ul>
</p></div>
  </div>
(snip)
    </div></span>

<br /></span>
</p>

The problem with this is that if a user includes an unordered list within their profile text, which is a reasonable thing to do, it generates an implied close of paragraph tag (generated by the browser) just before the ul. This then closes the inserted paragraph tag at the beginning of the profile so that the inserted close paragraph tag at the end of the content profile closes "content-profile-view" and at this point we are in a whole world of pain as the rest of the page unravels.

The paragraph tags need to be removed and replaced with divs to avoid this situation.

This is occurring on Firefox 3 but the Eclipse HTML editor agrees with the interpretation. The doctype is as follows:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

Comments

yellek’s picture

yellek commented

content_profile.module, lines 368 and 369 should be changed to:

    $content['#prefix'] = '<div id="content-profile-view">';
    $content['#suffix'] = '</div>';
fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Active » Postponed (maintainer needs more info)

? Where does this additional

stem from? Imo no code should create a

without previously adding a

.

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Postponed (maintainer needs more info) » Fixed

I 've overlooked you mentioned it'S (generated by the browser)

-> I don't think so. A browser doesn't change the page it is rendering. I suppose it's coming from your node theme or so. So I don't think there's a bug.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

chromeyellow’s picture

chromeyellow commented

The original poster's bug and diagnosis may or may not be precisely accurate.

However, wrapping the entire output the the content profile in p tags is an unwise decision. I suggest that the fix in #1 should be given more consideration.