= Description =

Placing certain (innocuous) markup in the description part of a definition item causes white space to be inserted between the term and the description.

== Steps to reproduce ==
 1. Start a definition list
 1. In the definition part of an entry, include a link or ''any'' kind of format modifier (emphasis, underline, monospaced, other?

== Example ==
{{{
 Definition1:: has only plain text.
 Definition2:: Contains ''Italic'' text.
 Definition3:: There's something '''bold''' here.
 Definition4:: Throw in another plain one
 Definition5:: And it's a [:MoinMoinBugs:link] now.
 Definition6:: Try a bit of `typewriter text`
 Definition7:: And end off with more plain text
}}}

 Definition1:: has only plain text.
 Definition2:: Contains ''Italic'' text.
 Definition3:: There's something '''bold''' here.
 Definition4:: Throw in another plain one
 Definition5:: And it's a [[MoinMoinBugs|link]] now.
 Definition6:: Try a bit of `typewriter text`
 Definition7:: And end off with more plain text

<<BR>>

== Component selection ==

standard HTML rendering.
{{{
<dd>
  <p class="line862">
  Try a bit of <tt class="backtick">typewriter&nbsp;text</tt>
  <span class="anchor" id="line-26"></span>
</dd>
...
<dd>
  And end off with more plain text
  <span class="anchor" id="line-27"></span>
  <span class="anchor" id="line-28"></span>
</dd>
}}}

So the different rendering is caused by: 
{{{
  <p class="line862">
}}}

== Details ==

|| '''!MoinMoin Version''' || 1.5.8 ||
|| '''OS and Version''' || this site ||
|| '''Browser''' || ie 6 ||

== Workaround ==
 * Manually format your definition lists
 * Refrain from using any modifiers in the definition part
 * Pretend you don't notice

'''Manual Formatting''' <<BR>>`     `Now I ''can'' put __anything__ I [[want]] <<BR>>
'''Another one''' <<BR>>`     `Now '''this''' is more like it. <<BR>>


= Discussion =
Not directly related, but relevant... I've tried to hunt down problems in the rendered HTML several times, and it seems to me that the pervasive use of the line-number based classes really makes it difficult to understand what's going on.  Is this really the best way to do it, or is there a less obfuscated method that could be used?

= Plan =
## This part is for Moin``Moin developers:

 * Priority: 
 * Assigned to:
 * Status: this will be fixed in moin2 because of the dom tree used there

----
## If you are a moin core developer, replace the category to Category* in these cases:
## Category MoinMoinNoBug - if this is not a bug.
## Category MoinMoinBugConfirmed - if you can confirm the bug on current code.
## Category MoinMoinBugFixed - after the bug is fixed in current code.
CategoryMoinMoinBug CategoryForMoin2