nextcloud / nextcloud/passman-webextension
List of incompatible websites
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 119
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
List of incompatible websites, for which the save banner and/or the autofill function do not work properly.
Doesn't work : The passman extension don't autofill
https://login.aliexpress.com
https://accounts.google.com
https://twitter.com/
Need refresh : The Passman extension displays the banner for the password saving request after a browser refresh
https://www.burgerking.fr/
https://espace-personnel.direct-assurance.fr/
https://discord.com/
TrueNAS Gateway
https://ubiwebauth.ubisoft.com/ (Good luck)
Only manually : The Passman extension don't displays any banner for the password saving request, but work if save manually
https://anilist.co/
https://www.creditmutuel.fr/
https://account.jetbrains.com/login
https://XXX.freeboxos.fr/ / http://mafreebox.freebox.fr/ (This is a french internet box gateway, you can't acces it)
https://login.live.com/ (Pretty badly)
https://login.nvgs.nvidia.com/
https://parsec.app/
https://www.paypal.com/signin (Pretty badly)
https://panel.preyproject.com/app (Pretty badly)
Configuration
Operating system: Windows 11
Browser: Brave Version 1.45.127 Chromium: 107.0.5304.110 (Build officiel) (64 bits)
With aggressive privacy settings, except on some websites that broke.
Extensions that might cause interference: Don't think so
Passman version: 2.4.2
Extension version: 2.1.2
Nextcloud version: 24.0.2
Browser log
Ask if needed
Contributor guide
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
The report names affected login sites and describes autofill and save-banner failures, but it does not identify a source file, test, or entry point. Start by reproducing one listed failure with the stated browser and extension versions, then inspect the extension's content-script handling for that site; done means a confirmed fix with regression coverage for the affected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100