[blink-dev] Re: Intent to Extend Experiment: JavaScript Promise Integration

2025-01-29 Thread 'Francis McCabe' via blink-dev
nterpoint might be that we expect to learn something > important and new in this extension that we haven't learned in the previous > OT windows, which would be somewhat surprising, but can happen. Is that > likely? > > Best, > > Alex > > On Monday, January 27, 2025 at 1

[blink-dev] Intent to Extend Experiment: JavaScript Promise Integration

2025-01-27 Thread Francis McCabe
Contact emails...@chromium.org Explainer https://github.com/WebAssembly/js-promise-integration/blob/main/proposals/js-promise-integration/Overview.md Specification https://github.com/WebAssembly/js-promise-integration/blob/main/proposals/js-promise-integration/Overview.md Design docs https://doc

[blink-dev] Re: Intent to Extend Experiment: JavaScript Promise Integration

2024-10-16 Thread Francis McCabe
Hi Alex Some small responses: 1. We currently have around 120 OT registrants. We have had some informal feedback, including from Meet — who are planning to use JSPI as part of their effort to migrate to WebGPU. 2. Agreed that we can ping Webkit now. Will do soon. 3. The process for the CG hing

Re: [blink-dev] Intent to Extend Experiment: JavaScript Promise Integration

2024-06-24 Thread 'Francis McCabe' via blink-dev
T? > > Best, > > Alex > > On Mon, Jun 24, 2024, 1:47 PM 'Francis McCabe' via blink-dev < > blin...@chromium.org> wrote: > >> I am 'ok' with a shorter extension. I asked for 6 months because I >> foresee a reasonable risk of needing

Re: [blink-dev] Intent to Extend Experiment: JavaScript Promise Integration

2024-06-24 Thread &#x27;Francis McCabe' via blink-dev
at? 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? > > Thanks, >Rick > > On M

[blink-dev] Intent to Extend Experiment: JavaScript Promise Integration

2024-06-24 Thread Francis McCabe
Contact emails...@chromium.org Explainer https://github.com/WebAssembly/js-promise-integration/blob/main/proposals/js-promise-integration/Overview.md Specification https://github.com/WebAssembly/js-promise-integration/blob/main/proposals/js-promise-integration/Overview.md Design docs https://doc

Re: [blink-dev] Re: Intent to experiment - WebAssembly JavaScript Promise Integration (update)

2024-02-20 Thread &#x27;Francis McCabe' via blink-dev
;> >> On Thu, Jan 25, 2024 at 10:29 AM Mike Taylor >> wrote: >> >>> Yep - that is an official positive signal, thanks! >>> On 1/24/24 7:40 PM, Francis McCabe wrote: >>> >>> Does this: >>> https://mozilla.github.io/standards-p

[blink-dev] Re: Intent to experiment - WebAssembly JavaScript Promise Integration (update)

2024-01-24 Thread Francis McCabe
Does this: https://mozilla.github.io/standards-positions/#wasm-js-promise-integration count as an official positive signal? Francis On Wed, Jan 24, 2024 at 3:09 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > > > On Friday, January 5, 2024 at 7:25:28 PM UTC+1 Franc

Re: [blink-dev] Intent to experiment - Wasm JavaScript Promise Integration

2024-01-10 Thread &#x27;Francis McCabe' via blink-dev
ls" for > web developer interest. There's not much point in doing the overhead of an > OT unless we have at least one developer who wants to test out the > functionality in a production environment. Can you elaborate? > > Thanks, > Rick > > On Fri, Jan 5, 2024

[blink-dev] Intent to experiment - WebAssembly JavaScript Promise Integration (update)

2024-01-05 Thread Francis McCabe
This is an update to the previous intent-to-experiment (filled out a few more fields) Contact emails...@chromium.org Explainer https://github.com/WebAssembly/js-promise-integration/blob/main/proposals/js-promise-integration/Overview.md Specification https://github.com/WebAssembly/js-promise-inte

[blink-dev] Intent to experiment - Wasm JavaScript Promise Integration

2024-01-05 Thread Francis McCabe
Contact emails...@chromium.org Explainer https://github.com/WebAssembly/js-promise-integration/blob/main/proposals/js-promise-integration/Overview.md Specification https://github.com/WebAssembly/js-promise-integration/blob/main/proposals/js-promise-integration/Overview.md Summary Stack Switchin

[blink-dev] Intent to Prototype: Stack Switching Promise Integration

2022-05-26 Thread &#x27;Francis McCabe' via blink-dev
eature/5674874568704000 This intent message was generated by Chrome Platform Status <https://chromestatus.com/>. -- Francis McCabe SWE -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop re

[blink-dev] Re: Intent to Ship: WebAssembly Content Security Policy

2021-10-06 Thread &#x27;Francis McCabe' via blink-dev
here would be removing that > allow-list but keeping the behaviour for extensions otherwise the same? > > On Thursday, September 23, 2021 at 10:36:20 PM UTC+1 Francis McCabe wrote: > >> Contact emailsad...@chromium.org >> f...@chromium.org >> >> Explainer >&g

Re: [blink-dev] Intent to Ship: WebAssembly Content Security Policy

2021-10-05 Thread &#x27;Francis McCabe' via blink-dev
ve talked about this approach in WebAppSec a few times, and I think > there's general agreement on the approach. I'd like to see the spec > language land before shipping this, but it looks like there aren't any > substantive outstanding questions, and I'm confident you ca

[blink-dev] Intent to Ship: WebAssembly Content Security Policy

2021-09-23 Thread Francis McCabe
Contact emailsad...@chromium.org f...@chromium.org Explainer https://github.com/WebAssembly/content-security-policy/blob/master/proposals/CSP.md Specificationhttps://github.com/w3c/webappsec-csp/pull/293 Design docs https://github.com/WebAssembly/content-security-policy/blob/master/proposals/CSP

Re: [blink-dev] Intent to Prototype: WebAssembly Content Security Policy

2021-09-02 Thread Francis McCabe
The proposed change is very small and not 'architectural'. The proposal adds a new policy keyword to CSP and extends the role (slightly) of script-src itself. On Thu, Sep 2, 2021 at 6:43 AM Yoav Weiss wrote: > > > On Wed, Sep 1, 2021 at 9:00 PM Francis McCabe wrote: &g

[blink-dev] Intent to Prototype: WebAssembly Content Security Policy

2021-09-01 Thread Francis McCabe
Contact emailsad...@chromium.org f...@chromium.org Explainer https://github.com/WebAssembly/content-security-policy/blob/master/proposals/CSP.md Specificationhttps://github.com/w3c/webappsec-csp/pull/293 Summary Enhancements to Content Security Policy to improve interoperability with WebAssembl