What file chunks establish: a 768 KiB bridge is not resumable upload or a receipt

Chunks crossing a WebKit bridge do not prove the destination saved a complete file

attachFiles reads up to 768 KiB raw data per chunk, base64-encodes bridge arguments, then asks the page’s own file control to accept them. JS accumulates parts and constructs File objects. Chunking proves neither constant memory everywhere nor server streaming/resume. attached is a page-stage result, not remote completion or sending.

Different from mixed batches, manifests and protection

Batches concern placement order, manifests concern local visibility, protection concerns writes. Here native-to-JS-to-input stages matter. No real attachment is read/uploaded and no transfer service is added.

Check Verified scope Manual review Not established
Native reads Up to 768 KiB with offset Local read/errors Server resume offset
Base64 Bridge string encoding Overhead versus transfer stage Raw bytes equal all RAM
JS staging incoming/parts accumulate into File Page memory versus local file Constant memory across all sides
Chunk response Per-chunk Bool can fail Local acceptance versus service Backend saved every chunk
Final control Page input/accept conditions Actual control/service limits Every site/type/size supported
Page boundary isTrusted etc. on this path Not all text-path conditions transfer All channels have identical guards
Discard Clear helper IDs Local staging versus remote copies Recall a prior service upload
Budget/result Local staging/attached separately Actual stage/remaining items 200 MiB staging guarantees site acceptance

Synthetic chunk note

Known: helper accepted several sample chunks. Unknown: final input/service status. Do not report upload complete or infer nothing happened from later failure. Keep the intended page stable and inspect actual results rather than renaming types/replaying batches.

Avoiding one giant JS string is implementation intent, not total-memory/speed/background-resume SLA. No general server upload/recovery protocol or device/network benchmark is supplied here.

FAQ

Are chunks server streaming?

No. Native-to-JS and site-to-service are different stages.

Is 768 KiB a whole-memory limit?

No. Base64/parts/File and other allocations remain.

Does attached prove server storage?

No. Page acceptance differs from remote evidence.

Does discard recall a remote attachment?

No. Clearing helper state does not establish recall.

Does 200 MiB staging certify every site?

No. Inputs/services retain limits and permissions.

Was upload/resume tested?

No. Fixed source only, without a transfer/transcoding/resume feature.

Reading and source

Batch stages · Local visibility · File protection · Start · Privacy

Attachment/chunk flow · Parts/input adaptation · Staging budget