ScreenTinker 255d8c0600 feat(#109): implement PiP close_button on Android (was a documented no-op) ... The server forwarded close_button (routes/pip.js) and it's in openapi.yaml, but no player rendered it — Tizen deferred "close-button focus" as non-MVP, the web player has none, and Android's PipOverlay never read the flag. So the documented field did nothing on any device. Implement it on Android: when close_button:true, a tappable ✕ floats at the box's top-right in a FrameLayout wrapper that is a SIBLING of the box — so it isn't clipped by the box outline or dimmed by the overlay opacity. Tapping it clears THIS overlay (id-matched via the captured token). Only the ✕ is clickable; the rest of the full-screen pipLayout stays touch-transparent, so taps elsewhere fall through to the playing content (no input regression). Verified on the emulator over live YouTube: the ✕ renders at the corner, and tapping it removes the overlay while the video keeps playing. Parity note: web/Tizen players still don't implement close_button; D-pad focus of the ✕ on non-touch TV hardware is intentionally not wired (MVP = touch/pointer, matching the Tizen focus deferral). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-06-19 14:45:14 -05:00
..
104-draft-preview-build-plan.md	feat(preview): draft-aware device-free playlist preview via player reuse (#104)	2026-06-15 14:11:05 -05:00
109-android-pip-visibility.md	feat(#109): implement PiP close_button on Android (was a documented no-op)	2026-06-19 14:45:14 -05:00
android-troubleshooting.md	docs: add Android player troubleshooting & recovery guide	2026-06-03 19:58:09 -05:00
local-ai-setup.md	docs: local AI setup guide for the Content Designer (#41)	2026-06-09 13:57:02 -05:00
multi-tenancy-design.md	Phase 1: multi-tenancy design doc + migration scripts	2026-05-11 19:37:15 -05:00
openapi.yaml	docs(api): document /api/pip and the assignments muted field (#109/#129)	2026-06-18 17:36:12 -05:00