Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2023-05-04 Meeting Notes #50

Open
jasnell opened this issue May 4, 2023 · 2 comments
Open

2023-05-04 Meeting Notes #50

jasnell opened this issue May 4, 2023 · 2 comments

Comments

@jasnell
Copy link
Contributor

jasnell commented May 4, 2023

Today's call was a light agenda, largely catching up on current status

  • Andreu: updates on the status of
  • 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
@jasnell
Copy link
Contributor Author

jasnell commented May 4, 2023

@panva
Copy link

panva commented May 4, 2023

Ad (self-)certification/wpts

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants