Should disabled extensions have their `runtime.setUninstallURL` opened on uninstall?
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 711
- Forks
- 95
- Avg merge
- 10d 11h
- Merged PRs (30d)
- 2
Description
The question pretty much covers it but I couldn't find any documented expected behavior so I'm opening this issue to find consensus. This Chromium issue was the impetus behind raising this.
In Chrome, runtime.setUninstallURL is opened even if an extension was disabled before being removed. This differs from Firefox, where disabling an extension prevents the uninstall URL from opening upon removal.
Does the WECG have a preference for standardizing this behavior? Chrome developers are open to changing this (adding an early bailout for disabled extensions) to improve developer consistency.
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
Start with the linked Chromium issue and the MDN documentation for runtime.setUninstallURL, then compare the described Chrome and Firefox behaviors. Done means the WECG reaches and records a consensus on whether disabled extensions should open the uninstall URL.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100