42491f7724
When I refactored this out into a vfunc, I forgot to change the code that interprets the result flags to actually respect the new FRAME_SHAPE_CHANGED result flag. Since we weren't ever clearing the frame bounds, this meant that the "shadow clip" wasn't ever updated as a result. Since right now all Wayland surfaces are considered ARGB32, we always clip shadows under frames, and thus shadows had this weird "punch-out" from the first frame shape.