The 0.18 to 0.19 migration guide has no entry for the ImageNode rendering change introduced in bevyengine/bevy#24154
0.19 added ImageNode::visual_box (VisualBox), defaulting to VisualBox::ContentBox. In 0.18, an ImageNode's image was drawn over the node's full bounds; in 0.19 it is drawn only within the content box — i.e. inset by the node's border and padding.
Any node combining an ImageNode with nonzero padding (or border) renders differently after upgrading, with no compile error or warning. I ran into this with the exact use case that motivated bevyengine/bevy#24150: a 9-sliced button background with padding used to inset a text label. After upgrading, the sliced background shrinks to hug the label and the padding appears to no longer work.
The 0.18 to 0.19 migration guide has no entry for the
ImageNoderendering change introduced in bevyengine/bevy#241540.19 added
ImageNode::visual_box(VisualBox), defaulting toVisualBox::ContentBox. In 0.18, anImageNode's image was drawn over the node's full bounds; in 0.19 it is drawn only within the content box — i.e. inset by the node'sborderandpadding.Any node combining an
ImageNodewith nonzeropadding(orborder) renders differently after upgrading, with no compile error or warning. I ran into this with the exact use case that motivated bevyengine/bevy#24150: a 9-sliced button background with padding used to inset a text label. After upgrading, the sliced background shrinks to hug the label and the padding appears to no longer work.