Run placement code if the geometry restore is invalid
The following discussion from !259 (merged) should be addressed:
There's a potential behavioural difference compared to the old code:
Previously if the savedGeometry wasn't valid it would do:
Whereas now we're explicitly it in the top left. That sounds like it has potential to be annoying?
I like that we're sending the 0 sized configure event to the client so it chooses, but is it worth adding some flag to place the client in the next
Currently, if the geometry restore is invalid. The window will be placed at the upper left screen corner if the window is restored or has left the fullscreen mode. We need to run the placement code to find a better position.