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

End round bracket in html detailed single line method docs is wrong colour. (Origin: bugzilla #632426) #3983

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

Comments

@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

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

On 2010-10-18 03:52:07 +0000, Cleo Saulnier wrote:

Overview:

Ridiculously trivial end round bracket is wrong colour on prototypes displayed on a single line in detailed docs using default html style. If the prototype is displayed on several lines, the end round bracket shows up the correct colour.

Actual Results:

Constructor & Destructor Documentation

template<class T, class Pr = std::less<T>, class R = RNG>
SkipList< T, Pr, R >::SkipList ( &# 160;) [inline]

Expected Results:

Constructor & Destructor Documentation

template<class T, class Pr = std::less<T>, class R = RNG>
SkipList< T, Pr, R >::SkipList ( &# 160;) [inline]

Take a look at the two lines with the round brackets.

      <td>(</td>
      <td class="paramname">&# 160;)</td>

See how the closing one has "paramname" as a classname and the opening bracket doesn't. I'm guessing this is what is causing the different colours. Happens with any amount of arguments as long as the whole prototype is displayed on a single line (minus the template stuff).

On 2010-11-30 20:18:07 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2011-01-03 19:01:14 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.3. 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 as completed Jul 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant