Closed
Bug 1229937
Opened 9 years ago
Closed 4 years ago
Figure out handling of ui tour for addons (pocket specifically)
Categories
(Firefox :: Pocket, defect)
Firefox
Pocket
Tracking
()
RESOLVED
INACTIVE
| Tracking | Status | |
|---|---|---|
| firefox45 | --- | affected |
People
(Reporter: mixedpuppy, Unassigned)
References
Details
Followup for bug 1215694 Some code is left over in UI tour for pocket, we need to either remove ui tour for pocket or move ui tour support into the addon.
|
||
Comment 1•8 years ago
|
||
Does this need to happen before pocket-as-system addon moves to release? Is that work that you would do or do we need to bring in another team?
Flags: needinfo?(mixedpuppy)
|
Reporter | |
Comment 2•8 years ago
|
||
This doesn't need to happen before release. This is probably first a product/architecture decision. Do we want to allow system addons an ability to modify/add to the UI tour? Or do we just want to change the UI tour core code when we want to showcase functionality in a system addon (this is what we essentially have now).
Flags: needinfo?(mixedpuppy)
|
||
Comment 3•4 years ago
|
||
This bug has been closed due to inactivity and/or the potential for this bug to no longer be an issue with the new Discovery Stream-powered New Tab experience, and improvements to Pocket’s integration with Firefox.
Please help us triage by reopening if this issue still persists and should be addressed.
Thanks!
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•