ScreenTinker 80c9d81c26 fix(widgets): honest webpage-widget note — blocked sites don't work on device ... The webpage-widget preview note claimed: "the site blocks embedding in a browser — it will still display on the device screen." The second half is false. The widget renders the URL in an <iframe> (renderWebpage), and the device player loads that page in a Chromium WebView, so a site sending X-Frame-Options / CSP frame-ancestors (Amazon, Google, most large sites/banks) is refused on the device exactly as in the browser preview. The note set the wrong expectation — a customer (and we) chased CORS and "should work on device" when the live device screen was blank too. Reword to tell the truth in all 6 languages (en/es/fr/de/it/pt), both the frontend i18n key (widget.webpage_blocked_note) and the player's preview_webpage_blocked string: if the preview is blank the site blocks embedding and won't display on the device either — try a page that allows it. Copy-only; no behaviour change. This is not an Amazon-side fix (embedding refusal is the site's choice) — just accurate messaging. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-07-24 19:14:01 -05:00
..
debug-overlay.js	Add player debug overlay and server-side error telemetry sink	2026-05-15 15:20:42 -05:00
index.html	fix(widgets): honest webpage-widget note — blocked sites don't work on device	2026-07-24 19:14:01 -05:00
sw.js	feat: transition engine — GL wipes across web, Tizen & Android (+ image↔video) (#204)	2026-07-20 16:45:32 -05:00