GUIFadeLabel.cs does use a wrong width for the renderable area on the first rendered frame before the scroll delay is over. Users can see a visibile glitch when a button is not selected after the set delay. The text at the end fades out more.

Reason: When the control's width for scrolling is set, it is missing a +5, which is a magical number used throughout the SkinEngine for label width.

These magical numbers cause additional glitches like faded text rendered a few pixels outside a button. But as skins relay largely on these hardcoded values removing them (which we should) is a larger undertaking.