Note to self: Partial workaround is MainWindow.set_default_size(700, 550) instead of remembered window size, but it still doesn't solve the issue, when user maximizes window before entering to Grooveshark/Google Play. It's also regression in user experience. This black magic should be commited unless the upstream bug is fixed in the next stable WebKitGTK release (1.8).
Note to self: Partial workaround is MainWindow. set_default_ size(700, 550) instead of remembered window size, but it still doesn't solve the issue, when user maximizes window before entering to Grooveshark/Google Play. It's also regression in user experience. This black magic should be commited unless the upstream bug is fixed in the next stable WebKitGTK release (1.8).