You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be a bug (or at least an unexpected result from a developer perspective), when creating a text node with "word wrapping" applied to it (i.e. a width property and contain property set to both).
When the text content is larger than the width property, everything works as expected. But whenever the text content is smaller than the desired word wrapping width, the final width of the texture reported in the text loaded event is not the actual text width, but equals the value of the supplied width).
From a developer perspective, one would expect that the width property is interpreted as a max width, and the returned width to be actual width of the final texture.
The text was updated successfully, but these errors were encountered:
There seems to be a bug (or at least an unexpected result from a developer perspective), when creating a text node with "word wrapping" applied to it (i.e. a
width
property andcontain
property set toboth
).When the text content is larger than the width property, everything works as expected. But whenever the text content is smaller than the desired word wrapping width, the final width of the texture reported in the text loaded event is not the actual text width, but equals the value of the supplied
width
).From a developer perspective, one would expect that the
width
property is interpreted as a max width, and the returnedwidth
to be actual width of the final texture.The text was updated successfully, but these errors were encountered: