WICG / WICG/PEPC

Could there be a PEPC-light?

Open
#63 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Bikeshed
Stars
72
Forks
15
PR merge metrics
No merged PRs in 30d

Description

The main issues that this proposal is trying to solve is "permission regret" or "leading to unintended grants as well as unintended denials of critical capabilities".

This should be solved with improved browser UI. However, if reprompting is desirable it can also be solved by "only" requiring stronger signals of user intent. That is, without requiring a new element with specified styling and a lot of checks. It could specify that a button click is required and that this permission may only be requested once every X seconds.

Is there any data on how often sites abuse users by over-requesting permissions which suggests that such a simplified protection would not be enough?

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

No file or test is named. Start by reviewing the PEPC explainer and the issue's questions about stronger user-intent signals and abuse data; the issue does not define a concrete change or completion criterion.

Written by the indexing model from the issue text.

Assessment

Domain
security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.