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

Missing tooltip attribute for ref in compound.xsd (Origin: bugzilla #571964) #3273

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

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

On 2009-02-16 09:59:51 +0000, INgo Rah wrote:

The attribute tooltip is missing for refTextType makes XML parsers issue warnings and even stop working on the node.

--- orig/compound.xsd
+++ new/compound.xsd
@@ -100,6 +100,7 @@
<xsd:extension base="xsd:string">
<xsd:attribute name="refid" type="xsd:string" />
<xsd:attribute name="kindref" type="DoxRefKind" />

  •   <xsd:attribute name="tooltip" type="xsd:string"/>
      <xsd:attribute name="external" type="xsd:string" />

On 2009-12-20 20:41:40 +0000, wrote:

Apparently, this bug still exists still today (1.6.1). The fix is just adding this one line for the to compound.xsd - except of course if the tooltip attribute is not supposed to be used at all.

It seems that this bug makes a difference only if source code is inlined. The lines look like this:


A second bug in compound.xsd, in docSimpleSectType, e.g. for XPaths /doxygen/compounddef/sectiondef/memberdef/detaileddescription/para/simplesect, as seen in the following snippet of a class xml:



The problem is that the XSD does not allow in this place.

On 2009-12-22 15:03:59 +0000, Dimitri van Heesch wrote:

Confirmed. I'll fix both issues in the next subversion update.

On 2009-12-30 13:39:01 +0000, Dimitri van Heesch wrote:

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).

@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