avm1: Correct `getBounds` properties order
This affects the order of the properties when enumerating the returned object (via `Enumerate2` etc.)
This commit is contained in:
parent
6ce88f24de
commit
3f5582ed94
|
@ -1506,8 +1506,8 @@ fn get_bounds<'gc>(
|
||||||
Some(activation.context.avm1.prototypes().object),
|
Some(activation.context.avm1.prototypes().object),
|
||||||
);
|
);
|
||||||
out.set("xMin", out_bounds.x_min.to_pixels().into(), activation)?;
|
out.set("xMin", out_bounds.x_min.to_pixels().into(), activation)?;
|
||||||
out.set("yMin", out_bounds.y_min.to_pixels().into(), activation)?;
|
|
||||||
out.set("xMax", out_bounds.x_max.to_pixels().into(), activation)?;
|
out.set("xMax", out_bounds.x_max.to_pixels().into(), activation)?;
|
||||||
|
out.set("yMin", out_bounds.y_min.to_pixels().into(), activation)?;
|
||||||
out.set("yMax", out_bounds.y_max.to_pixels().into(), activation)?;
|
out.set("yMax", out_bounds.y_max.to_pixels().into(), activation)?;
|
||||||
Ok(out.into())
|
Ok(out.into())
|
||||||
} else {
|
} else {
|
||||||
|
|
Loading…
Reference in New Issue