Thanks Chris. Here's the updated signals links (no replies yet on either): * WebKit: https://lists.webkit.org/pipermail/webkit-dev/2021-August/031958.html * Gecko: https://github.com/mozilla/standards-positions/issues/573
On Thursday, August 26, 2021 at 2:14:57 PM UTC-7 Chris Harrelson wrote: > Hi, two points: > > * This proposal appears to be only at phase 3 > <https://github.com/WebAssembly/proposals/blob/master/README.md>, which > is one lower than the "intent-is-rubber-stamped" level. If you wish to ship > now, please provide signals from the other implementations. > * Implementation signals must come from bit.ly/blink-signals. > > On Thu, Aug 26, 2021 at 12:18 PM Yoav Weiss <[email protected]> > wrote: > >> >> >> On Thursday, August 26, 2021 at 8:58:29 PM UTC+2 [email protected] >> wrote: >> >>> On Wednesday, August 25, 2021 at 3:56:34 PM UTC+2 [email protected] >>> wrote: >>> >>>> On Tuesday, August 24, 2021 at 11:04:33 AM UTC+2 Andreas Haas wrote: >>>> >>> Contact emails >>>>> >>>>> [email protected], [email protected], [email protected], >>>>> [email protected] >>>>> >>>> >>>>> Explainer >>>>> >>>>> https://github.com/aheejin/exception-handling >>>>> >>>>> Specification >>>>> >>>>> https://github.com/WebAssembly/exception-handling >>>>> >>>>> Summary >>>>> >>>>> This feature is adding exception support to WebAssembly. Exception >>>>> handling allows code to break control flow when an exception is thrown. >>>>> The >>>>> exception can be any exception known by the WebAssembly module, or it may >>>>> be an unknown exception that was thrown by a called imported function. >>>>> >>>>> >>>>> Blink component >>>>> >>>>> Blink>JavaScript>WebAssembly >>>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EJavaScript%3EWebAssembly> >>>>> >>>>> Search tags >>>>> >>>>> wasm <https://chromestatus.com/features#tags:wasm>, webassembly >>>>> <https://chromestatus.com/features#tags:webassembly>, Exceptions >>>>> <https://chromestatus.com/features#tags:Exceptions> >>>>> >>>>> TAG review >>>>> >>>>> Not required for WebAssembly feature launches >>>>> >>>>> TAG review status >>>>> >>>>> Not applicable >>>>> >>>>> Risks >>>>> >>>>> Interoperability and Compatibility >>>>> >>>>> Gecko: Positive (https://bugzilla.mozilla.org/show_bug.cgi?id=1335652 >>>>> <https://chromestatus.com/admin/features/launch/4756734233018368/5?intent=1> >>>>> ) >>>>> >>>> Looks like they shipped (or at least fully implemented), so that's >>>> definitely a strong signal :) >>>> >>> >>> We have an incomplete implementation (available behind a flag in >>> Nightly, not on by default even there) and have not in any sense shipped >>> anything. We do not (to my knowledge) have any publicly stated position on >>> this spec, apart from that bug and an intent-to-prototype. >>> >> >> Apologies. I read too much into the issue marked as FIXED. >> >> >>> --lars >>> >>> >>>> >>>>> >>>>> WebKit: Positive They're probably not likely to begin working on the >>>>> proposal before stage 3 >>>>> >>>> >>>> Links? >>>> >>>> >>>>> >>>>> Web developers: The developer feedback on the spec proposal ( >>>>> https://github.com/WebAssembly/exception-handling) was positive. This >>>>> feature is one of the last bits missing to port legacy c++ apps to the >>>>> web. >>>>> Code that uses WebAssembly Exception Handling can be generated by >>>>> Emscripten <https://emscripten.org/docs/porting/exceptions.html> and >>>>> has been used successfully in the origin trial. >>>>> >>>>> >>>>> Debuggability >>>>> >>>>> Supported using DevTools >>>>> >>>>> >>>>> Is this feature fully tested by web-platform-tests >>>>> <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> >>>>> ? >>>>> >>>>> Yes, tests are provided by the spec, see >>>>> https://github.com/WebAssembly/exception-handling/tree/master/test. >>>>> >>>>> Flag name >>>>> >>>>> WebAssembly Exception handling can be enabled and disabled by the V8 >>>>> Flag: --experimental-wasm-eh. >>>>> >>>>> >>>>> Requires code in //chrome? >>>>> >>>>> No >>>>> >>>>> Tracking bug >>>>> >>>>> https://bugs.chromium.org/p/v8/issues/detail?id=8091 >>>>> >>>>> Launch bug >>>>> >>>>> https://bugs.chromium.org/p/chromium/issues/detail?id=1173515 >>>>> >>>>> Estimated milestones >>>>> >>>>> OriginTrial desktop first >>>>> >>>>> 90 >>>>> >>>>> OriginTrial desktop last >>>>> >>>>> 94 >>>>> >>>>> OriginTrial android first >>>>> >>>>> 90 >>>>> >>>>> OriginTrial android last >>>>> >>>>> 94 >>>>> >>>>> >>>>> Link to entry on the Chrome Platform Status >>>>> >>>>> https://chromestatus.com/feature/4756734233018368 >>>>> >>>>> Links to previous Intent discussions >>>>> >>>>> Intent to Experiment: >>>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/7l3oDJuNs6o/m/MtlFURU1BAAJ >>>>> >>>> >>>> Any conclusions/feedback from the Origin Trial? >>>> >>>> >>>>> >>>>> >>>>> This intent message was generated by Chrome Platform Status >>>>> <https://www.chromestatus.com/>. >>>>> >>>> -- >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/92a38cf6-cd34-430a-bb1f-56dbae947a2fn%40chromium.org >> >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/92a38cf6-cd34-430a-bb1f-56dbae947a2fn%40chromium.org?utm_medium=email&utm_source=footer> >> . >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/bcf0dd08-92ce-4a9f-807d-6978783feeb9n%40chromium.org.
