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 655591 - Comment causes failure in <ul> processing
Comment causes failure in <ul> processing
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.4
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2011-07-29 19:02 UTC by Bill
Modified: 2011-08-14 14:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Glossary template with commented out list items to be filled in. (2.14 KB, application/octet-stream)
2011-07-29 19:02 UTC, Bill
Details

Description Bill 2011-07-29 19:02:21 UTC
Created attachment 192884 [details]
Glossary template with commented out list items to be filled in.

The following HTML:

<ul>
<!--   <li></li> -->
</ul>

gives failure:

<li> tag but found <ul> instead!
C:/Morita/MIMIR Dirs/MIMIR-20110712/doxydoc/Glossary.dox:170: warning: unexpected end of comment while looking for a html list item

It looks like the "<li>" gets process in spite of being within a comment.

Browsers seem to process the HTML sequence without issue.

Was creating the skeleton for a Glossary
Comment 1 Dimitri van Heesch 2011-08-02 12:55:13 UTC
An empty <ul> list is not really valid HTML anyway, but I'll make the warning more clear and make sure valid output is generated nevertheless.
Comment 2 Bill 2011-08-02 17:12:20 UTC
The fact that the issue was discovered in an empty <ul></ul> is not the issue.
The issue is that there was any type of HTML directive processed with the body of a valid comment.

This will likely be an issue for other directives that have been commented out as well.
Comment 3 Dimitri van Heesch 2011-08-02 21:02:16 UTC
The <li> was correctly ignored because it was part of a comment, but as a result a </ul> was found while the parser was looking for a <li>. The warning incorrectly mentioned a <ul> was found, where in fact a </ul> was found.
Comment 4 Dimitri van Heesch 2011-08-14 14:04:34 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.5. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.