After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 595931 - <p> </p> Tags are added to every cell in a HTML table
<p> </p> Tags are added to every cell in a HTML table
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.6.1
Other Solaris
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2009-09-22 10:39 UTC by Jens Bastian
Modified: 2009-12-30 13:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jens Bastian 2009-09-22 10:39:09 UTC 
In a HTML table, <p> and </p> tags are added to every cell by doxygen. Thus the spacing between two rows of the table becomes too large.

Example:

<table>
<tr>
<td>name</td>
<td>text</td>
</tr>
<tr>
<td>name</td>
<td>text</td>
</tr>
</table>

is transformed by doxygen to

<table border="1" cellspacing="3" cellpadding="3">
<tr>
<td><p>name </p>
</td><td><p>text  </p>

</td></tr>
<tr>
<td><p>name </p>
</td><td><p>text  </p>
</td></tr>
</table>
Comment 1 Craig Scott 2009-12-11 00:12:18 UTC 
I can confirm this bug and it makes generating table header rows annoyingly difficult. You can't get a header row to have a height of one line, since the <p> tags have the effect of adding a second line to the cell height.

Interestingly, if the cell contains an unordered list (ie <ul> tags) then no <p> tags are inserted. Presumably doxygen is only inserting <p> tags if it determines that there's some ordinary text in the cell that is not subject to some other kind of formatting.
Comment 2 Dimitri van Heesch 2009-12-24 13:03:58 UTC 
Confirmed. Should be fixed in the next release.
Comment 3 Dimitri van Heesch 2009-12-30 13:39:05 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.2. Please verify if this is indeed the case and reopen the
bug if you think it is not fixed (include any additional information that you
think can be relevant).