fix: use JPEG SOI/EOI marker scanning instead of multipart parsing

Browse Source

Recording now scans the fetch response for JPEG start-of-image (0xFFD8)
and end-of-image (0xFFD9) markers instead of parsing multipart boundaries.
This is more robust because:
- No dependency on boundary format quirks
- No crossOrigin attribute needed (no canvas tainting issues)
- JPEG SOI/EOI markers are reliable frame delimiters per the JPEG spec

Also added cancelRecording() cleanup at start of each new recording.

...

This commit is contained in:

李傲琦

2026-08-01 16:48:44 +08:00

parent 88caa1e976

commit 786230036b

3 changed files with 95 additions and 74 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

dist/assets/index-3GYuRNvV.js → dist/assets/index-C5dzEsTl.js

Vendored

+1 -1

File diff suppressed because one or more lines are too long