Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Blob and File serialization steps drop the type attribute (all engines keep it; WPT asserts it)

未关闭
#226 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 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::WriteDOMObject writes the blob's uuid, type and size (kBlobTag), and File's type with its other fields.
  • WebKit: SerializedScriptValue.cpp: CloneSerializer writes blob->type() after the URL (BlobTag) and file.type() (FileTag), and readFile passes the type to File::deserialize.
  • Gecko: StructuredCloneHolder.cpp: WriteBlob keeps a reference to the BlobImpl (which holds the content type), and ReadBlob wraps 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 of value's type attribute."
  • Blob deserialization steps: add "Initialize the value of value's type attribute to serialized.[[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

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

w3c/FileAPI 的其他 Issue

查看 w3c/FileAPI 的全部 Issue

相似的 Issue

更多 Web Dev Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。