Spike: can Studio's WebView (WKWebView) decode device-view frames at 15 fps or more?

Aperta
#448 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
57/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
flutter, go
Ambito
mobile, testing-qa

Direzione di ricerca

The issue names no repository files; start by locating Studio’s Wails WebView harness and the device view hub that accepts loopback WebSocket connections. Rerun the harness in an unlocked, visible macOS session and record rendered fps and decode time for each frame size. Done means reporting the measurements and whether 603x1311 frames reach 15 fps without dropped-frame growth.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area/studio documentation

Question: can a page opened in Studio's Wails WebView on macOS (WKWebView) connect to ws://127.0.0.1, receive JPEG frames and decode them with createImageBitmap at 15 fps or more?

What was run (2026-10-14)

A small native host (a WKWebView in an AppKit window, the page served from a custom wails://wails/ scheme as Wails does) and a loopback Go server that streams real JPEG frames (a photographic image at 402x874, 603x1311 and 1206x2622 portrait sizes: 23, 41 and 118 KiB at quality 60; and a UI screenshot: 15, 27 and 83 KiB), paced at 30 fps and acknowledged-as-fast-as-decoded. The page decodes each frame with createImageBitmap(new Blob([bytes],{type:"image/jpeg"})), draws it on a canvas and reports rendered frames, drops, decode and draw time.

Result

  • Answered: a page whose origin is wails://wails connects to ws://127.0.0.1:<port> and the server sees Origin: wails://wails, which the device view hub allows. No mixed-content or custom-scheme block.
  • Not answered: the decode rate. The Mac's screen was locked during the run, so the window reported document.hidden === true and WebKit stopped running the page's timers after the first 6 second step. That step, 402x874 frames at a 30 fps pace, rendered 106 of 185 received frames (about 17.7 per second) in a hidden window, which is not a valid measurement. A visible window is needed.
  • A second route (Playwright's WebKit build, headless) was started but its browser download did not finish in the time available, so no WebKit number exists yet.

To finish

Run the same harness on an unlocked session (or with Playwright WebKit) and report fps and decode ms per size. Acceptance for the device view: at least 15 fps rendered at 603x1311 JPEG without dropped-frame growth.

Nothing was installed on the machine besides the throwaway harness; no code is proposed in the repository for this spike.

Lingua principale
Go
Stelle
6
Fork
3
Merge medio
6h 28m
PR unite (30g)
362

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di AlphaWaveSystems/flutter-probe

Tutte le issue di AlphaWaveSystems/flutter-probe

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.