1.8 KiB
id, title, status, assignee, created_date, updated_date, labels, dependencies, parent_task_id, priority
| id | title | status | assignee | created_date | updated_date | labels | dependencies | parent_task_id | priority |
|---|---|---|---|---|---|---|---|---|---|
| TASK-20.1 | Refactor overlay runtime to use per-layer window bounds ownership | Done | 2026-02-12 08:47 | 2026-02-13 08:04 | TASK-20 | medium |
Description
Refactor overlay runtime so each overlay layer owns and applies its bounds independently. Keep tracker geometry as shared origin input only.
Acceptance Criteria
- #1
updateOverlayBoundsServiceno longer applies the same bounds to every overlay window by default. - #2 Main runtime/manager exposes per-layer bounds update paths for visible and invisible overlays.
- #3 Window tracker updates feed shared origin data; each layer applies its own computed bounds.
- #4 Single-layer behavior (visible-only or invisible-only) remains unchanged from user perspective.
Implementation Notes
Started implementation for per-layer overlay bounds ownership refactor.
Implemented per-layer bounds ownership path: visible and invisible layers now update bounds independently through overlay manager/runtime plumbing, while preserving existing geometry source behavior.
Replaced shared all-window bounds application with per-window bound application service and layer-specific runtime calls from visibility/tracker flows.
Archiving requested by user.
Final Summary
Refactored overlay bounds ownership to per-layer update paths. Tracker geometry remains shared input, but visible/invisible windows apply bounds independently via explicit layer routes. Existing single-layer UX behavior is preserved.