WICG / WICG/js-self-profiling

How does document policy work in workers?

Open
#33 10 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
207
Forks
17
PR merge metrics
No merged PRs in 30d

Description

In a worker you do not have access to a document which would make step 3 of profile() fail to compile or some such.

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

Start with the profile() algorithm, especially step 3, and check how its document-policy assumptions apply in a worker where no document is available. Review the current issue discussion to determine the intended worker behavior; done means the policy and affected step are clarified in the proposal.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.