First of all, it would be an editor bug.
The debugger (any of them) only delivers the content of the window (as text), but nothing else.
I stand corrected. I thought it might be FpDebug related because I was debugging and the value being shown had to come from the debugger but, I can see how the debugger may not have anything to do with the location and color of the window.
The yellow hint is created using IpTurboProDsg package => so if uninstalled, the grey hint is used. Yet, then all hints would be grey.
There are no "user-installed" packages in this installation. IOW, this installation is as-is "out of the box". I've seen the color difference other times, I don't know if in this case the "&" had something to do with it but, I've had other occasions where the window was unexpectedly grey instead of yellow and there were no variables nor fields involving an "&". Should the occasional difference in color be reported as a bug ?
On Windows, if you have more than one screen, and they have different DPI settings, and a window on one screen is focused, but the mouse hovers over a window on another screen, the wrong dpi is used to calculate the hint offset. => Btw, such DPI mixes even affect apps like the windows explorer, to have incorrect display in some cases...)
This installation is in a VM with a single monitor. IOW, I don't think different DPIs have something to do with the location of the window.
So, at this time, I say this is primarily a codetools bug, but there may be additional issues in the hint handling code...
Ultimately that's what matters, should any of this be reported as a bug, what part should be considered a bug and, lastly against what ?
I'll create a ticket if one is warranted.