>> 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-positi
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
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 at 1
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
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
674874568704000
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 receiving
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
>> https://gith
oach 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 can work out the
> details.
>
> -mike
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
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:
>
>>
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
11 matches
Mail list logo
