Closed: containers-do-not-bind and pointer-needs-a-container-or-a-screen. Both were the same defect seen from two sides, and both are fixed by assigning windows by pid -- two sessions now hold two outputs with a real browser on each, and the pointer aims at a desk that has something in it. The cursor item is rewritten with the answer rather than the speculation: the compositor draws no cursor image for a virtual pointer, so no capture setting can make one appear. The evidence is in the file, including the three wrong answers that came before it and the boring measurement that settled it. New item: killing a session left two browsers alive, found by counting windows rather than sessions.
1.9 KiB
1.9 KiB
TODO
Known, unfixed problems — each one real, none of them guessed at.
Each file answers three questions and stops:
- The issue — what is actually wrong, with the evidence for it.
- Ideas — more than one, and which one is the recommended route.
- Why it matters — the impact, not the principle.
| item | severity | state |
|---|---|---|
| cursor-visibility-in-captures | high | answered: the compositor draws no cursor for a virtual pointer. Needs a decision on an overlay marker |
| scroll-has-no-compositor-proof | medium | works live; unproven in a gate |
| reconcile-while-containers-are-off | medium | partly fixed: discovery now survives a restart; teardown still lives inside the feature |
| kill-can-leave-the-app-alive | medium | found by counting windows, not sessions |
Closed since this folder was written:
- "Containers do not bind" — fixed. Windows are assigned by the pid the compositor reports, moved onto their desk's workspace and read back. Two sessions now hold two outputs with a real browser on each.
- "The pointer is unusable while containers are off" — fixed with it. The pointer aims at the session's desk, and desks hold applications.
- "Discovery refuses when two compositor instances exist" — fixed. Each candidate is asked for its version and the one that answers is used.
Severity here means "how much of the feature is actually delivered", not "how loud the failure is". The highest is highest because a whole class of work is blocked on it: the pointer is exact and invisible, so nothing can show where anything happened.
When one of these is fixed, delete its file and the row — this folder is a list of what is still true, not a history of what was thought.