Blob and File serialization steps drop the type attribute (all engines keep it; WPT asserts it)
還沒有人認領這個 Issue。
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 74/100
- Issue 類型
- 缺陷
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- html, javascript
- 領域
- web-dev
研究方向
Read the Blob and File serialization and deserialization sections in the File API specification, then inspect WPT's compare_Blob in html/webappapis/structured-clone/structured-clone-battery-of-tests.js. Update the four algorithms to preserve type and verify the structured-clone, postMessage, and IndexedDB cases pass.
由索引模型根據 Issue 內容生成。
描述
The serialization and deserialization steps for Blob and File don't carry the type attribute, but every engine keeps it and WPT asserts it.
What the spec says
Blob's serialization steps set serialized.[[SnapshotState]] and serialized.[[ByteSequence]], and the deserialization steps restore only those two. File's steps add [[Name]] and [[LastModified]]. None of the four algorithms mentions type, so read literally:
structuredClone(new Blob(["x"], { type: "text/plain" })).type // "" by the spec text
structuredClone(new File(["x"], "a.txt", { type: "text/plain" })).type // "" by the spec text
The same holds for postMessage, history.pushState, and IndexedDB's StructuredSerializeForStorage.
What engines do
All three keep the type ("text/plain" above):
- Blink:
V8ScriptValueSerializer::WriteDOMObjectwrites the blob's uuid, type and size (kBlobTag), and File's type with its other fields. - WebKit:
SerializedScriptValue.cpp:CloneSerializerwritesblob->type()after the URL (BlobTag) andfile.type()(FileTag), andreadFilepasses the type toFile::deserialize. - Gecko:
StructuredCloneHolder.cpp:WriteBlobkeeps a reference to theBlobImpl(which holds the content type), andReadBlobwraps the same impl, so the type carries over.
Tests
WPT's compare_Blob (html/webappapis/structured-clone/structured-clone-battery-of-tests.js) asserts actual.type === input.type for every cloned Blob and File, across the structured-clone, postMessage and IndexedDB variants.
Proposal
- Blob serialization steps: add "Set
serialized.[[Type]]to the value ofvalue'stypeattribute." - Blob deserialization steps: add "Initialize the value of
value'stypeattribute toserialized.[[Type]]." - File serialization and deserialization steps: the same two steps.
Possibly related: #98 (whether a clone copies or references the data), which doesn't cover type.
Found while implementing structured serialization for Blob and File in Crane, a web platform engine, which keeps the type as the engines do.
- 主要語言
- HTML
- 星號
- 118
- 分支
- 52
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
w3c/FileAPI 的其他 Issue
-
TPAC2026
難度 2/5 1-3 小時 新手友好度 68/100
-
難度 2/5 1-3 小時 新手友好度 68/100
-
難度 1/5 1 小時以內 新手友好度 62/100
-
難度 2/5 1-3 小時 新手友好度 68/100
-
難度 5/5 一週以上 新手友好度 30/100
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 65/100
rescript-lang/rescript-lang.org#1411 ·
維護者通常 2 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 82/100
chthollyphile/folia-major#520 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 82/100
databuddy-analytics/Databuddy#1106 ·
維護者通常 1 天內回覆
-
frontend
難度 1/5 1 小時以內 新手友好度 72/100
Paul-Austin-Oswego-CSC480-HCI521/gift-app#116 ·
維護者通常 2 天內回覆