Sub-Window host/port design bug?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 9.7k
- Forks
- 565
- PR merge metrics
- No merged PRs in 30d
Description
Unfortunately, it is quite simple (and common) to remove the parent after creating a new window. After that, host/parent sync cannot work because the parent widget was removed (see SUB_WINDOW_HOST_TO_PARENT, SUB_WINDOW_PARENT_TO_HOST commands)
Attached is a simple example which triggers the bug.
[window-problem.rs.txt](https://github.com/linebender/druid/files/8095785/window-problem.rs.txt)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the attached window-problem.rs example and trace the SUB_WINDOW_HOST_TO_PARENT and SUB_WINDOW_PARENT_TO_HOST commands after the parent widget is removed. Reproduce the failure, then determine the intended host/parent synchronization behavior and add coverage showing that removing the parent no longer breaks sub-window handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100