You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
James: Web Crypto Streams is still absolutely something we'd like to see move forward. Paused on it a bit to see if the new W3C WG activity around web crypto was going to gain momentum. We definitely want to see it move forward this year tho.
Luca: Deno is +1 on Web Crypto Streams, particularly digest
Andreu: Littledan asked about whether the minimum common api should be defined around ShadowRealm global scope?
James: Not sure that actually helps. We should discuss but knee jerk reaction is no.
Ethan: Regarding minimum common api and runtime keys, there is a proposal to add a new "wintercg" runtime key to identify runtimes that conform to the minimal standard... problem with that is we need a way of certifying/verifying that the runtime actually is compliant
James: Need to identify the subset of the web platform tests that cover the minimum api.
Ethan: self-certification to those is likely the best option.
(basically we need to identify the subset and have a tool for self-reporting that a runtime is compliant, and after they do they can make use of the "wintercg" runtime key)
James: speaking of minimum common API, we'd like to add performance.now() and performance.timeOrigin to the minimum. Seeing it used in many more places.
Todo's coming from the call
Further investigate certification of web platform tests to minimum common API
Get fetch call rescheduled in calendar to conform to the new monthly schedule
Open PR for adding performance.now and performance.timeOrigin
Feedback needed on runtime keys "wintercg" proposal
The text was updated successfully, but these errors were encountered:
Consider working with the wpt dashboard project to create wintercg interop dashboards like so https://wpt.fyi/interop-2022?stable only with the wintercg runtimes pre-selected and a different wpt subset shown. Alternatively running a fork of the dashboard and report processor just for wintercg. Deno and Node already submit synced results to wpt.fyi daily. Other runtimes can also do so. Having undergone the process for adding wpt reports for Node recently I can give pointers.
Today's call was a light agenda, largely catching up on current status
Todo's coming from the call
The text was updated successfully, but these errors were encountered: