Repository navigation
Hotfix: New window freeze and garbled psql borders on Windows - #102
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two Windows bugs from 2.2.6.
open_new_windowwas a synchronous command building a webview window, which deadlocks the main thread on Windows (Deadlock creating a new window on the IPC handler on Windows tauri-apps/wry#583). It is async now, and the new window gets the main window's navigation guard, zoom and devtools settings and theme backdrop.linestyle=unicodeborders as UTF-8 while the Windows console reads its output as code page 1252, so│showed as│. On Windows psql keeps its ASCII borders and NULL shows as(null).cargo checkand the terminal tests pass. Not yet tried on a Windows machine.