w3c / w3c/webcrypto

Reconsider "in parallel"?

Open
#389 20 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
294
Forks
78
PR merge metrics
No merged PRs in 30d

Description

From WebKit's source code:

The 11 December 2014 version of the specification suggests we should perform the following task asynchronously:
https://www.w3.org/TR/WebCryptoAPI/#SubtleCrypto-method-importKey
It is not beneficial for less time consuming operations. Therefore, we perform it synchronously.

This came up in #368 first.

It's probably worth writing some tests to see when the promises are getting resolved relative to the running task.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read the WebCrypto API importKey specification linked in the issue and the discussion in #368, focusing on the meaning of performing the task asynchronously. Add tests that observe when the returned promises resolve relative to the running task, and use those results to determine whether the current behavior matches the specification.

Written by the indexing model from the issue text.

Assessment

Tech stack
html, javascript
Domain
api, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.