position and rotation are in reference to the parent, so a one level component will reference the file axis. Each child (sub group or sub component ) references its parent, whereas size is the current object or nesting. you can have the XY, seemly flipped with the LenX, LenY due a rotation.
This is why its best to not only have the attribute dialog of parent and child, but also have the option dialog open showing that the parent is selected, when altering the position or rotation attributes, otherwise the object is going to fly off to some original or new reference position.
Rotation can still be problematic to find the correct sequence as the there is a redraw after each entry, this will cause a “flyoff”
various workflow / workaround maybe to wrap each rotation, or have an attribute reference them, or play around with the values until you achieve the correct balance. Then exit and do a redraw to have all the references work within their environment.
I kind of look at it as parallel worlds that have worm holes due to us trying to influence the outcome