The “Collection Promo” section is wrongly redisplayed on the first opened new tab after being dismissed using the “Delete from Pocket”/”Archive in Pocket” options
Categories
(Firefox :: New Tab Page, defect, P4)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox73 | --- | unaffected |
firefox74 | --- | unaffected |
firefox75 | --- | wontfix |
firefox76 | --- | wontfix |
People
(Reporter: mheres, Assigned: thecount)
References
Details
(Keywords: regression)
Attachments
(1 file)
3.43 MB,
image/gif
|
Details |
[Affected Versions]:
- Firefox Nightly 75.0a1 Build ID: 20200309091841
[Affected Platforms]:
- Windows 10 x64
- macOS 10.15
- Linux Mint 19.2 Tina
[Prerequisites]:
- Have the value of the pref
browser.newtabpage.activity-stream.discoverystream.spocs-endpoint
set tohttps://spocs.getpocket.com/spocs?site=1116390&country=US®ion=US-CA
. - Have the value of the pref
browser.search.region
set toUS
. - Be logged into Pocket.
[Steps to reproduce]:
- Open the browser with the profile from prerequisites and open a new tab.
- Click the “Open menu” button of a Collection card and select the “Save to Pocket” option.
- For the same card, click the “Open menu” button and select the “Delete from Pocket” option.
- Repeat steps 2 and 3 for three more cards to dismiss the section.
- Open a new tab and observe the behavior.
[Expected results]:
- The “Collections Promo” section is no longer displayed.
[Actual results]:
- The “Collections Promo” section is redisplayed.
[Notes]:
- This issue is also reproducible if using “Archive in Pocket” instead of “Delete from Pocket” in the steps above.
- The section is dismissed after opening another new tab.
- This issue is not reproducible if the “Dismiss” option of a card is used instead.
- This issue is not reproducible if the section is dismissed from the section “Dismiss” button.
- The
browser.newtabpage.activity-stream.discoverystream.isCollectionDismissible
pref does not affect the results for either of its values. - Possibly caused by Bug 1621023.
- Attached is a recording of the issue.
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
This is happening because the archive/save then delete actions don't update the preloaded tab.
They could, but I suspect this is something we can live with for the experiment.
@tawanda is that true, can we live with this for the experiment?
Assignee | ||
Comment 2•5 years ago
|
||
Also, to re test this, you can enable newtab devtools, then go about:newtab#devtools-ds and click "refresh cache" and the collection comes back to be tested again.
Assignee | ||
Comment 3•5 years ago
|
||
Also probably worth noting, I'm pretty sure I was reproducing this on regular stories, and not just collections.
Comment 4•5 years ago
|
||
We're good to launch the experiment with this behavior. We can pick this up as part of a bigger bucket of dismiss/delete function work. :thecount :maria.heres
Reporter | ||
Comment 5•5 years ago
|
||
@Scott, I have tested the scenario mentioned in comment 3 and I can confirm the normal and SPOC stories from the “Recommended by Pocket” section are also redisplayed in a new tab after being dismissed using “Delete from Pocket” and “Archive in Pocket”.
Comment 6•5 years ago
|
||
Bugbug thinks this bug is a regression, but please revert this change in case of error.
Comment 7•5 years ago
|
||
(In reply to Tawanda Kanhema from comment #4)
We're good to launch the experiment with this behavior. We can pick this up as part of a bigger bucket of dismiss/delete function work. :thecount :maria.heres
Should we adjust then priority/severity for this bug?
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Comment 8•5 years ago
|
||
Updating Severity from minor
to P4
per May 4th changes to Severity field and triage process.
Comment 9•3 years ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:daleharvey, since the bug has high priority, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•3 years ago
|
Assignee | ||
Comment 10•3 years ago
•
|
||
I'm just going to wont-fix this.
Collection promos are a currently not running feature, and the user impact of this bug is minimal anyway even if it were running.
Description
•