Open
Bug 1412295
Opened 7 years ago
Updated 2 years ago
A sideloaded extension which overrides the default search page will never display the secondary prompt
Categories
(WebExtensions :: General, enhancement, P5)
WebExtensions
General
Tracking
(firefox57 wontfix)
REOPENED
Tracking | Status | |
---|---|---|
firefox57 | --- | wontfix |
People
(Reporter: bsilverberg, Assigned: mkaply)
Details
This is an issue I noticed when looking for the cause of bug 1412291. Currently, if an extension overrides the default search, and it does so using a new engine (as opposed to one of the built-in engines), it displays an extra prompt to the user asking them to confirm they want to change the default search engine. This only happens on initial install - it doesn't happen when an extension is enabled, and that makes sense in most cases, as we don't want to prompt the user again for something they've already allowed. The problem is that when sideloading an extension it gets installed in the background and the only action a user takes is to enable it after that. When a user enables the extension for the first time they are not shown this extra prompt.
Reporter | ||
Comment 1•7 years ago
|
||
I'm not sure if this is a bug or not, but it seems like one to me. What do you think, Mike?
Flags: needinfo?(mozilla)
Updated•7 years ago
|
status-firefox57:
--- → wontfix
Updated•6 years ago
|
Priority: -- → P5
Assignee | ||
Comment 2•6 years ago
|
||
This effectively prevents sideloading add-ons from changing the search engine which is actually the behavior we want.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(mozilla)
Resolution: --- → WONTFIX
Comment 3•6 years ago
|
||
If that's the behavior that we want, then we need to add a test for it
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Assignee | ||
Comment 4•6 years ago
|
||
Do we have sideload tests today?
Comment 5•6 years ago
|
||
(In reply to Mike Kaply [:mkaply] from comment #4) > Do we have sideload tests today? Yes, many. You could do this with an xpcshell test that uses AddonTestUtils.manuallyInstall() and then AddonTestUtils.promiseStartupManager(). That would have to watch for the observables that we use to trigger notifications. Alternatively, you could write a mochitest that drops xpis into the profile and then runs (from chrome code) AddonManagerPrivate.getNewSideloads().
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → mozilla
Updated•6 years ago
|
Product: Toolkit → WebExtensions
Assignee | ||
Comment 6•4 years ago
|
||
We don't support sideloading anymore.
Status: REOPENED → RESOLVED
Closed: 6 years ago → 4 years ago
Resolution: --- → INVALID
Comment 7•4 years ago
|
||
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•