Spike: can Studio's WebView (WKWebView) decode device-view frames at 15 fps or more?
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 2/5
- Geschätzter Aufwand
- 1-3 Stunden
- Anfängerfreundlichkeit
- 57/100
- Issue-Typ
- Feature
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- flutter, go
- Bereich
- mobile, testing-qa
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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://wailsconnects tows://127.0.0.1:<port>and the server seesOrigin: 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 === trueand 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.
- Vorherrschende Sprache
- Go
- Sterne
- 6
- Forks
- 3
- Ø Merge
- 6 Std. 28 Min.
- Gemergte PRs (30 T.)
- 362
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus AlphaWaveSystems/flutter-probe
-
agent: is checked on a wrapper holding several checkables answers from the first one in tree orderOffenbug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
AlphaWaveSystems/flutter-probe#865 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area/cli bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 73/100
AlphaWaveSystems/flutter-probe#424 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area/docs documentation
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
AlphaWaveSystems/flutter-probe#409 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Dial timeout error should say how long it waited and name the timeout settingEvtl. vergeben @jay23606 hat das vor 2 Tagen übernommen. Offenarea/cli bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
AlphaWaveSystems/flutter-probe#408 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 45/100
AlphaWaveSystems/flutter-probe#888 ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in AlphaWaveSystems/flutter-probe
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
IBM-Cloud/terraform-provider-ibm#7115 ·
Maintainer antworten meist innerhalb von 2 Tagen
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 86/100
fluxcd/notification-controller#1441 ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 66/100
volcengine/volcengine-go-sdk#163 · 1 Kommentar ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
OneBusAway/maglev#2145 ·
Maintainer antworten meist innerhalb von 2 Tagen
-
priority/medium status/ready type/chore
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
discobox-ai/discobox#1357 ·
Maintainer antworten meist innerhalb von 1 Tag