57bb297450
Ugh. So in the fullscreen case, we need to make sure to specify that it's a MOVE_ACTION so that we move to the saved position, but we can't do that in the resizing case since we need to use the resized rectangle. The flags are really hurting us here. Perhaps we should make it the client's responsibility to specify a complete rectangle which we could resize to; then the weird-o logic would be self-contained in each front-end. I'm not convinced this covers all cases, especially when we could have a dangling weird state pointer, but it fixes our existing two testcases.