Secure context features

Open
#23 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
documentation, web-dev

Research direction

No file or test is named in the issue. Start by locating the standard text and its treatment of secure contexts, then compare it with the WinterCG common minimum API list; done means the standard explicitly states how WinterCG environments should be treated.

Written by the indexing model from the issue text.

Description

Many web platform features, including some of the ones in the WinterCG common minimum API list, are restricted to secure contexts (i.e. https websites). We should probably be explicit somewhere in the standard that WinterCG environments are generally meant to be treated similarly to secure contexts.

Dominant language
Bikeshed
Stars
308
Forks
17
No merged PRs in 30d

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.

More from WinterTC55/proposal-minimum-common-api

All issues in WinterTC55/proposal-minimum-common-api

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.