[WASM] CR transition for WebAssembly Web API

[binji]

Document title, URIs, estimated publication date

target: https://www.w3.org/TR/2019/CR-wasm-web-api-1-20190516/
source: http://webassembly.github.io/spec/web-api/
to be published with: Core and JavaScript Interface

Abstract

This document describes the integration of WebAssembly with the broader web platform.

Part of a collection of related documents: the Core WebAssembly Specification , the WebAssembly JS Interface , and the WebAssembly Web API .

Status

Standard bikeshed SOTD; no expected changes to implementations.

Decision to request transition

https://github.com/WebAssembly/meetings/blob/master/2019/WG-02-13.md#--request-that-we-move-forward-with-a-candidate-recommendation-cr

Changes

• compile a potential WebAssembly response makes a copy of the bodyArrayBuffer before performing asynchronous compile (step 2.7.1).

Requirements satisfied

N/A

Dependencies met

Normative references to WebAssembly JS API and WebAssembly Core Specification.

Wide Review

Reviewed with WebAssembly core specification, see list in #119.

Issues Addressed

Issues are addressed on http://github.com/WebAssembly/spec. See, for example, the following issues related to this specification:

• [spec] Normative: Support [Serializable] for WebAssembly.Module WebAssembly/spec#711
• [spec] Error type for fetch cancellation WebAssembly/spec#757
• [web-api] Download failure + lazy validate WebAssembly/spec#793
• Does WebAssembly.compileStreaming allow a Response as parameter? WebAssembly/spec#806
• Don't allow IndexedDB serialization of WebAssembly.Module WebAssembly/spec#821

Formal Objections

None.

Implementation

See results for 4 implementations at https://wpt.fyi/results/wasm/webapi.

• contenttype.any.*: some variants only pass on one implementation.

Patent disclosures

https://www.w3.org/2004/01/pp-impl/101196/status#current-disclosures

[binji]

@ericprud

[swickr]

Transition approved.

[plehegar]

Published
https://www.w3.org/TR/2019/CR-wasm-web-api-1-20190718/