It appears that the engine does not render TextLabels that are offscreen as an optimization.
However, if the Text extends beyond the bounds of the TextLabel itself, then the text will “pop” in once the edge of the label comes on screen.
The optimization needs to take the Text into account, not just the Label.
Here’s what I mean:
Here’s the repro file:
RichText_ScrollBug.rbxl (35.0 KB)
Hey boatbomber,
Thanks for including a minimum reproducible example with your report. As you mention, the observed issue is that text in TextLabels can go beyond the bounds of the label, but if the TextLabel goes off screen, the out of bounds text is not rendered. This behavior seems correct, as text should not be rendering if its TextLabel is off screen. Once it is on screen, it will then render and the text is allowed to go out of the TextLabel boundaries. If you believe I’m misunderstanding something, or if this is causing development issues for you please let me know.
The behavior seems unintuitive and undesirable to me. The GUI Instance should be displaying text on my screen, based on its given properties, but it isn’t because of this optimization.
At the very least, it should be explicitly and clearly documented on the TextLabel API page.
Hey boatbomber,
There is some ongoing internal discussion about this issue. I can’t promise any quick action, but a ticket has been made and the team will take a more in depth look at this in the near future.
Thanks again for the report!