microsoft / microsoft/msix-packaging
Per-domain passkey enumeration prompts degrade the experience of a MSIX-packaged browser
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 193
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 2
Description
Hi,
We are building a browser (https://duckduckgo.com/windows) installed using a MSIX installer. It deploys as a packaged app. For every single domain that supports passkeys, Windows asks the user separately whether they want to let us enumerate them. This degrades user experience and encumbers us compared to our competitors who install as unpackaged apps.
Would it be possible to incorporate a permission that skips these prompts, or at least consolidates them to be per-install instead of per-domain?
CC @petevb
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is identified in the issue. Start by reviewing the MSIX SDK's handling of packaged-app permission prompts and the passkey enumeration flow, then determine whether a per-install permission is supported or what design changes would be required. Done means documenting a viable permission behavior and its expected prompt scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100