Bug when viewing documentation panel for `nint/nuint.MaxValue/MinValue`

[sibber5]

Description

Title, screenshots below, seems to only affect nint/nuint.MaxValue/MinValue (IDE agnostic).

On .NET 9:

On .NET 8:

Reproduction Steps

Hover your mouse over any of the affected properties.

Expected behavior

For the documentation to show up properly.

Actual behavior

Documentation is missing words, and sometimes displaying unrelated stuff.

Regression?

No response

Known Workarounds

No response

Configuration

.NET 9 and 8
Windows 11 x64 latest major release

Other information

No response

[tannergooding]

CC. @gewarren, @BillWagner

What's the right place to look for resolving these types of issues and figuring out why the IntelliSense docs are out of sync from the XML docs in the source?

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-system-runtime
See info in area-owners.md if you want to be subscribed.

[gewarren]

For the .NET 8 text, presumably that incorrect text was fixed/updated for .NET 9, so I don't think that's an issue.

For the missing text, the IntelliSense XML file contains this:

    <member name="P:System.IntPtr.MaxValue">
      <summary>Gets the largest possible value of <xref data-throw-if-not-resolved="true" uid="System.IntPtr"></xref>.</summary>

Instead of something like:

Gets the largest possible value of <see cref="T:System.IntPtr" />.

I'm not sure if it's related to this internal work item, but I'll log a new issue as well and then update this text with the link.

[tannergooding]

Thanks!

Do we know how widespread the xref issue is?

[gewarren]

Tagging @carlossanlop since he generates the IntelliSense files. Carlos I think you might know why/when these xrefs are generated instead of see cref?

Do we know how widespread the xref issue is?

There are 194 occurrences in System.Runtime.xml, so pretty widespread. Another example:

[gewarren]

I think I know what's causing this bug (that is, inheriting docs from a type in a different namespace) and have logged an internal bug for the platform team.

I've also created an issue for myself to see if we can quickly work around the bug.

[gewarren]

Here's another somewhat related issue with paramrefs. The IntelliSense XML looks like this (instead of <paramref name="source" />):

<member name="M:System.Buffers.Binary.BinaryPrimitives.ReverseEndianness(System.ReadOnlySpan{System.Int128},System.Span{System.Int128})">
    <summary>Copies every primitive value from <code data-dev-comment-type="paramref">source</code> to <code data-dev-comment-type="paramref">destination</code>, reversing each primitive by performing an endianness swap as part of writing each.</summary>
    ...

And renders like this in IntelliSense:

Logged another (internal) bug.