Stack Switching denotes a technology that allows programs to suspend and resume computation. This is an active area that is part of the WebAssembly standards track. See https://github.com/WebAssembly/stack-switching and https://github.com/WebAssembly/meetings/tree/main/stack. This particular feature refers to the integration between JavaScript Promises and stack switching. This is described in more detail in https://docs.google.com/document/d/16Us-pyte2-9DECJDfGm5tnUpfngJJOc8jbj54HMqE9Y/edit#
This spec is backed by a standardization effort. We do not plan to ship the JSPI until it has been standardized by the W3C Wasm WG. However, post standardization, we will depend on all browsers implementing the standard.
Making use of JSPI requires some changes by WebAssembly-based developers (no impact on JavaScript developers). Depending on their toolchain usage a developer will need to modify their code. For Emscripten users, this is likely to be minimal as support for JSPI exists in Emscripten.
1. Control flow integrity. 2. Ensuring that JavaScript programs cannot suspend via JSPI.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
JSPI is part of a standards track effort. We are currently in 'stage 3' of a five stage process. The next stage (4) is when a specification is deemed final. There was a change in the API which we soft launched in M126 but we would like to formally switch to this new API in M129. (We had informed our users that we would be maintaining the old API through the end of the OT.) So, in summary there are two reasons for extending the origin trial: 1. We are not quite ready to move the spec to phase 4. This is for non-implementation reasons: we need to draft and review the specification text. 2. We would like to allow sufficient time for users to fully experiment with the new API. We anticipate being able to fully ship JSPI before the end of 2024, but also dont want to have to ask for yet another extension.
None.
Developers can piggyback on existing DevTools support for Promises to help with debugging JSPI applications. In particular the existing mechanisms for constructing extended stack traces from so-called Promise chains will also include stack traces from JSPI applications.
Origin trial desktop first | 123 |
Origin trial desktop last | 128 |
Origin trial extension 1 end milestone | 134 |
DevTrial on desktop | 109 |
OriginTrial Android last | 128 |
OriginTrial Android first | 123 |
OriginTrial webView last | 128 |
OriginTrial webView first | 123 |
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAE65UWBDn_Vvj5uqqOVMABJWopy_ZfOz4P5ZZYiqCxa7HACxCA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/46b78c6b-ae44-49ab-919c-3bd2194314f1n%40chromium.org.
Hi Francis,We only do OT extensions for 3 milestones at a time. It sounds like there's been a meaningful change in the API that we need to validate, so extending for another 3 to 131 sounds OK to me if you'd like to do that, but that gets you only to October.Outside of JS / WASM features, we generally do not block on standards maturity when shipping new APIs, since the chromium project has a policy of limiting the cost on velocity that we're willing to pay in order to reach standards consensus. What do you think the harm would be in shipping this now and coming up with a versioning and/or breaking change strategy for any changes which are deemed necessary after that? It sounds like you already have customers relying on this feature (given the commitments you mention around evolution of the API while in OT), so it's unclear whether shipping and iterating would really be all that different in practice?
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY9Kte1WKJVzPpMsnPMOj0vfBhqJ9XjiVi%3DNYyDm2TWy5g%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALi9WK-JJNTYSeNdSuai827Qg5%3D2vZo-emYP2z-5vJOfE%2B8Nng%40mail.gmail.com.