-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Description
Describe the bug
I have a program which creates 2 windows A and B.
After 2 seconds, A creates 2 children A_child1 and A_child2 using a tauri command.
Every window displays the windows it has access to using window.getAll(), and refreshes this list every 2 seconds.
The problem is that some windows can't access some others (see screenshot below).
The behaviour is really strange, and I think this has to do with timing. Even at the beginning, with the first 2 windows, it seems that A can't access B (see screenshot)
My fellow developper tried this out on Windows, and the effect is less weird (only A_child1 and A_child2 have issues) but it's still suspicious
Reproduction
- Download the reproduction example: https://github.com/armand-colin/tauri-issue-window-label
- Run it
Expected behavior
I'd expect that all the windows will have access to each other eventually. I'd expect some timing to kick in, but here the windows never appear in the list.
Platform and versions
Environment
› OS: Mac OS 13.0.0 X64
› Node.js: 14.19.1
› npm: 6.14.16
› pnpm: 6.11.0
› yarn: 1.22.15
› rustup: 1.25.1
› rustc: 1.65.0
› cargo: 1.65.0
› Rust toolchain: stable-x86_64-apple-darwin
Packages
› @tauri-apps/cli [NPM]: 1.1.1
› @tauri-apps/api [NPM]: 1.1.0
› tauri [RUST]: 1.1.1,
› tauri-build [RUST]: 1.1.1,
› tao [RUST]: 0.14.0,
› wry [RUST]: 0.21.1,
App
› build-type: bundle
› CSP: unset
› distDir: ../dist
› devPath: http://localhost:1420/
App directory structure
├─ node_modules
├─ src-tauri
├─ .git
├─ .vscode
└─ src
Stack trace
No response
Additional context
No response


