Closed
Bug 1519396
Opened 6 years ago
Closed 6 years ago
'Force Attribution' from ASRouter for Return to AMO does not work on Windows
Categories
(Firefox :: Messaging System, defect, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox66 | --- | verified |
People
(Reporter: vlad.jiman, Assigned: andreio)
References
Details
(Keywords: github-merged)
Attachments
(1 file)
|
(deleted),
text/x-github-pull-request
|
Details |
In order to force attribute and see the 'Add the Extension' page, which is the first page the user will see after installing Firefox with Return to AMO enabled, we use the asrouter - force attribute, method which currently only works on OSX.
Steps:
- Using a Nightly build go to about:config and set the following prefs:
- browser.newtabpage.activity-stream.asrouter.devtoolsEnabled = true
- browser.newtabpage.activity-stream.asrouter.providers.onboarding set to:
{"id":"onboarding","type":"local","localProvider":"OnboardingMessageProvider","enabled":true,"exclude":[]}
- Go to about:newtab#asrouter, Targeting tab and scroll to the bottom of the page
- Select Force Attribution and open a new tab with about:welcome url
Expected:
The iridium extension install page should be seen (or whichever extension was used with force attribution).
Actual:
For windows platforms the force attribution does not appear to do anything, so the FxA sign-on page is shown instead.
|
Reporter | |
Updated•6 years ago
|
|
|
Reporter | |
Updated•6 years ago
|
Summary: The API used to force attribution from ASRouter for Return to AMO does not work on Windows → 'Force Attribution' from ASRouter for Return to AMO does not work on Windows
|
||
Comment 1•6 years ago
|
||
|
||
Updated•6 years ago
|
Component: General → Activity Streams: Newtab
Product: WebExtensions → Firefox
|
||
Comment 2•6 years ago
|
||
Commit pushed to master at https://github.com/mozilla/activity-stream
https://github.com/mozilla/activity-stream/commit/2a10f2fb869835b5f3c7f45be8f38a773ac42304
Bug 1519396 - 'Force Attribution' from ASRouter for Return to AMO does not work on Windows (#4656)
|
||
Updated•6 years ago
|
Iteration: --- → 66.3 - Jan 7 - 20
Keywords: github-merged
|
Assignee | |
Comment 3•6 years ago
|
||
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
|
|
||
Comment 4•6 years ago
|
||
Target Milestone: --- → Firefox 66
|
|
||
Updated•6 years ago
|
Priority: -- → P1
|
|
Reporter | |
Comment 5•6 years ago
|
||
Validated using Windows 10 x64 bit with Nightly 66.0a1 build (20190120213632). The issue is no longer reproducing on this build.
Status: RESOLVED → VERIFIED
|
|
||
Updated•5 years ago
|
Component: Activity Streams: Newtab → Messaging System
You need to log in
before you can comment on or make changes to this bug.
Description
•