Closed
Bug 1992007
Opened 7 days ago
Closed 6 days ago
Update FollowSectionButtonHighlight component to show on first section (instead of second) section
Categories
(Firefox :: New Tab Page, enhancement)
Firefox
New Tab Page
Tracking
()
RESOLVED
FIXED
145 Branch
Tracking | Status | |
---|---|---|
firefox145 | --- | fixed |
People
(Reporter: maxx, Assigned: maxx)
References
Details
Attachments
(1 file)
Prefs
Set the following prefs to true
:
browser.newtabpage.activity-stream.asrouter.devtoolsEnabled
browser.newtabpage.activity-stream.discoverystream.sections.enabled
browser.newtabpage.activity-stream.discoverystream.personalization.enabled
_Note: You should not be following any topics _
Test scenarios:
- Open new tab
- Expected: The sections layout should be visible for Recommended Storieis (including the "Follow" button next to each topic)
- Navigate to
about:asrouter
and scroll down until you findTEST_NEWTAB_MESSAGE
- Replace the contents with the following JSON block:
{
"weight": 100,
"id": "TEST_NEWTAB_MESSAGE",
"template": "newtab_message",
"content": {
"messageType": "FollowSectionButtonHighlight",
"darkModeDismiss": true
},
"trigger": {
"id": "newtabMessageCheck"
},
"groups": [],
"targeting": "providerCohorts.panel_local_testing == \"SHOW_TEST\"",
"provider": "panel_local_testing"
}
- Click "Modify" (to submit this message data)
- Refresh new tab
- Expected: The FollowSectionButtonHighlight message should be visible, pointing to the FIRST "Follow" topic button
- Actual: The FollowSectionButtonHighlight message is visible and pointing to the SECOND "Follow" topic button
Assignee | ||
Comment 1•7 days ago
|
||
Pushed by mcrawford@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/a7974ab2f8a7
https://hg.mozilla.org/integration/autoland/rev/ac97f8abb684
Update FollowSectionButtonHighlight display logic r=home-newtab-reviewers,nbarrett
Status: NEW → RESOLVED
Closed: 6 days ago
status-firefox145:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 145 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•