[v3] Fix ordering of if branches in WebviewWindow.Restore method

[fbbdev]

Description

The Window.Restore method currently checks first whether the window is maximised, in which case it calls UnMaximise and returns, otherwise it proceeds to check whether it is in fullscreen mode or minimised.

This behaviour is both buggy and conceptually wrong:

• conceptually, it is possible for a window to be both maximised and in fullscreen mode, and typically fullscreen mode will have been entered after the window was maximised, hence the intuitive behaviour is to exit fullscreen first;
• practically, this results in a bug on macOS where restore does nothing in fullscreen mode, as it seems that the macOS windowing backend treats all fullscreen windows as also maximised.

Swapping the order of the branches fixes the problem on macOS.

To reproduce (on macOS):

• clone the PR branch,
• checkout the second-last commit (git checkout 3020b0a2f08),
• run the new window-api example,
• click the 'Fullscreen' button, then the 'Restore' button: nothing will happen.

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

I created the window-api example and used it to test most relevant combinations (maximise-then-restore, fullscreen-then-restore). I have not tested minimise-then-restore.

• Windows
• macOS
• Linux

Test Configuration

Wails CLI      | v3.0.0-alpha.3                                                                
Go Version     | go1.22.0                                                                      
Revision       | 12d12a33dec1d31f487b70f87bc31e80252f327c                                      
Modified       | true                                                                          
-buildmode     | exe                                                                           
-compiler      | gc                                                                            
CGO_CFLAGS     |                                                                               
CGO_CPPFLAGS   |                                                                               
CGO_CXXFLAGS   |                                                                               
CGO_ENABLED    | 1                                                                             
CGO_LDFLAGS    |                                                                               
DefaultGODEBUG | httplaxcontentlength=1,httpmuxgo121=1,tls10server=1,tlsrsakex=1,tlsunsafeekm=1
GOAMD64        | v1                                                                            
GOARCH         | amd64                                                                         
GOOS           | darwin                                                                        
vcs            | git                                                                           
vcs.modified   | true                                                                          
vcs.revision   | 12d12a33dec1d31f487b70f87bc31e80252f327c                                      
vcs.time       | 2024-02-21T12:40:32Z                                                          

# System
Name            | MacOS                                   
Version         | 12.6.6                                  
ID              | 21G646                                  
Branding        | Monterey                                
Platform        | darwin                                  
Architecture    | amd64                                   
Apple Silicon   | unknown                                 
CPU             | Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Xcode cli tools | 2395                                    
CPU             | Unknown                                 
GPU             | Unknown                                 
Memory          | Unknown                                 

# Diagnosis
 SUCCESS  Your system is ready for Wails development!

Checklist:

• I have updated mkdocs-website/docs/en/changelog.md with details of this PR
• My code follows the general coding style of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (N/A)
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[coderabbitai]

Important

Auto Review Skipped

Auto reviews are disabled on base/target branches other than the default branch. Please add the base/target branch pattern to the list of additional branches to be reviewed in the settings.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository.

To trigger a single review, invoke the @coderabbitai review command.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[leaanthony]

Not sure if I'm doing something wrong here but clicking restore when in fullscreen doesn't unfullscreen it... I wonder what I'm doing wrong 🤔

[fbbdev]

I am gonna clone the branch and test it again from a clean slate, let's see what happens

[fbbdev]

I've done the tests, here's what I see:

• repo at fix-restore, working tree clean, working dir is v3
• git checkout 3020b0a2f085cd
• go clean . && go clean -cache
• cd examples/window-api
• go run . –> long build time –> the restore button does nothing in fullscreen
• git checkout fix-restore
• go run . –> short build time –> the restore button still does nothing in fullscreen
• cd ../.. && go clean . && go clean -cache
• cd examples/window-api
• go run . –> long build time –> the restore button now works in fullscreen

Looks like the go build system is failing to pick up the changes 🤔

[leaanthony]

Looks like the go build system is failing to pick up the changes 🤔

Oh that suuuucks!

[leaanthony]

Yup! That worked great. Thank you!! 🙏