Issue metadata
Sign in to add a comment
|
WebAssembly Response API support |
||||||||||||||||||||||||||||||||||||||||||||
Issue descriptionChange description: Adds Response based origin bound variants for WebAssembly compilation and instantiation. Changes to API surface: * Adds WebAssembly.compileStreaming(response) * Adds WebAssembly.instantiateStreaming(response) Where response is always Promise.resolved with the expectation of a Response object (throws TypeError otherwise). Links: Proposal agreed on: https://github.com/WebAssembly/design/blob/master/Web.md Public standards discussion: https://github.com/WebAssembly/design/pull/991 Support in other browsers: Internet Explorer: No Edge: Public support, but no implementation Firefox: Public support, but no implementation Safari: Public support, but no implementation
,
May 22 2017
,
Jul 13 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e1628530d4237e822cd2c3125ab476ea87281d30 commit e1628530d4237e822cd2c3125ab476ea87281d30 Author: Mircea Trofin <mtrofin@chromium.org> Date: Thu Jul 13 23:17:40 2017 [wasm] Enable Response APIs by default. Intent to ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/T8r1SrZUEZM Bug: chromium:711083 Change-Id: Ieb9c7b3fcf76d6b13ef0c89d676cecf02b0daa78 Reviewed-on: https://chromium-review.googlesource.com/513531 Reviewed-by: Brad Nelson <bradnelson@chromium.org> Reviewed-by: Jochen Eisinger <jochen@chromium.org> Commit-Queue: Mircea Trofin <mtrofin@chromium.org> Cr-Commit-Position: refs/heads/master@{#486524} [modify] https://crrev.com/e1628530d4237e822cd2c3125ab476ea87281d30/content/public/common/content_features.cc [modify] https://crrev.com/e1628530d4237e822cd2c3125ab476ea87281d30/third_party/WebKit/LayoutTests/NeverFixTests
,
Jul 16 2017
,
Jul 19 2017
,
Jul 19 2017
This is only available on Window, not WorkerGlobalScope. Is this correct?
,
Jul 20 2017
For the moment, yes. In worker cases, the API would have little value until we start exploring transparent caching.
,
Jul 20 2017
If this API is called and the response fails because of content security policy, the tab crashes (Aw, snap!)
,
Jul 20 2017
Thanks - what csp is that, so I can try to repro it precisely?
,
Jul 20 2017
Test. Why is it deleting messages?
,
Aug 31 2017
This feature is targeted for M61 Stable and M61 is going to stable next week. Cross functional bits are either not flipped or missing info. Pls punt this feature to appropriate next milestone.
,
Aug 31 2017
Thomas, could you please help with the cross-functional bits?
,
Aug 31 2017
This feature has no impact on accessibility, legal, privacy, or UI, flipping those bits now to NA
,
Aug 31 2017
The security was LGTMed by Jochen in the intent to ship, flipping that bit now
,
Aug 31 2017
We have tests located here https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/http/tests/wasm_streaming/wasm_response_apis.html?q=wasm_respo&sq=package:chromium&l=1 Flipping test flag now.
,
Aug 31 2017
,
Sep 5 2017
|
|||||||||||||||||||||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||||||||||||||||||||
Comment 1 by bradnelson@chromium.org
, Apr 13 2017