Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comment causes failure in <ul> processing (Origin: bugzilla #655591) #4348

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.7.4 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2011-07-29 19:02:21 +0000, Bill wrote:

Created attachment 192884
Glossary template with commented out list items to be filled in.

The following HTML:

gives failure:

  • tag but found
      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 "

    • " 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

  • On 2011-08-02 12:55:13 +0000, Dimitri van Heesch wrote:

    An empty

      list is not really valid HTML anyway, but I'll make the warning more clear and make sure valid output is generated nevertheless.

    On 2011-08-02 17:12:20 +0000, Bill wrote:

    The fact that the issue was discovered in an empty

      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.

      On 2011-08-02 21:02:16 +0000, Dimitri van Heesch wrote:

      The

    • was correctly ignored because it was part of a comment, but as a result a was found while the parser was looking for a
    • . The warning incorrectly mentioned a
        was found, where in fact a
      was found.

    • On 2011-08-14 14:04:34 +0000, Dimitri van Heesch wrote:

      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.

      @doxygen doxygen closed this Jul 2, 2018

      Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
      You can’t perform that action at this time.