Closed Bug 1972421 Opened 6 months ago Closed 6 months ago

Add OMC Highlight to Follow Button in Sections Layout

Categories

(Firefox :: New Tab Page, enhancement)

enhancement

Tracking

()

VERIFIED FIXED
142 Branch
Tracking Status
firefox141 --- verified
firefox142 --- verified

People

(Reporter: maxx, Assigned: maxx)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Whiteboard: [hnt])

Attachments

(6 files, 3 obsolete files)

48 bytes, text/x-phabricator-request
Details | Review
48 bytes, text/x-phabricator-request
Details | Review
48 bytes, text/x-phabricator-request
Details | Review
48 bytes, text/x-phabricator-request
Details | Review
48 bytes, text/x-phabricator-request
Details | Review
48 bytes, text/x-phabricator-request
Details | Review
Assignee: nobody → mcrawford
Status: NEW → ASSIGNED
Depends on: 1972931
Pushed by nbarrett@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/7f5ac75dccdb https://hg.mozilla.org/integration/autoland/rev/6bb8141ea1a0 Add strings for Follow Section Button Highlight r=home-newtab-reviewers,fluent-reviewers,bolsson,npypchenko,nbarrett https://github.com/mozilla-firefox/firefox/commit/8977887259e8 https://hg.mozilla.org/integration/autoland/rev/3eab13ee94ac Add Follow Section Button Highlight message component r=home-newtab-reviewers,npypchenko https://github.com/mozilla-firefox/firefox/commit/a9a971a6ef37 https://hg.mozilla.org/integration/autoland/rev/8b27e915ed89 Add test coverage for FollowSectionButtonHighlight component r=home-newtab-reviewers,npypchenko
Status: ASSIGNED → RESOLVED
Closed: 6 months ago
Resolution: --- → FIXED
Target Milestone: --- → 142 Branch
Attachment #9496588 - Flags: approval-mozilla-beta?

firefox-beta Uplift Approval Request

  • User impact if declined: None
  • Code covered by automated testing: no
  • Fix verified in Nightly: no
  • Needs manual QE test: no
  • Steps to reproduce for manual QE testing: n/a
  • Risk associated with taking this patch: low risk
  • Explanation of risk level: Updates the strings used for a newtab callout
  • String changes made/needed: newtab-section-follow-highlight-title = Fine-tune your feed newtab-section-follow-highlight-subtitle = Follow your interests to see more of what you like.
  • Is Android affected?: no
Attachment #9496589 - Flags: approval-mozilla-beta?
Attachment #9496590 - Flags: approval-mozilla-beta?

firefox-beta Uplift Approval Request

  • User impact if declined: Will not be able to display follow highlight
  • Code covered by automated testing: yes
  • Fix verified in Nightly: no
  • Needs manual QE test: yes
  • Steps to reproduce for manual QE testing: et the following prefs to true: browser.newtabpage.activity-stream.asrouter.devtoolsEnabled browser.newtabpage.activity-stream.discoverystream.sections.personalization.enabled browser.newtabpage.activity-stream.discoverystream.sections.enabled Additional notes: You'll want to open the Browser Console to see any errors. Start with a fresh profile if possible Test scenarios: Interacting with the topic selection modal Open new tab Expected: The recommended stories feed should be in the "Section" layout with a "Follow" button at the top-right of each section Expected: There should be NO callout visible Open about:asrouter Cmd+F/Scroll down to TEST_NEWTAB_MESSAGE Replace "DownloadMobilePromoHighlight" with "FollowSectionButtonHighlight" in this box and click "MODIFY" button Open a new new tab Expected: The Follow Button callout should be visible only on second section Additional edge cases / testing: If you click the "X" of the highlight, the message should show as BLOCKED in about:asrouter If you are already following one store, this message should not be visible (regardless of message)
  • Risk associated with taking this patch: Low
  • Explanation of risk level: Will not affect other code, just enables us to use this new messaging
  • String changes made/needed: n/a
  • Is Android affected?: no
Flags: qe-verify+
Attachment #9496592 - Flags: approval-mozilla-beta?
Attachment #9496593 - Flags: approval-mozilla-beta?
Attachment #9496594 - Flags: approval-mozilla-beta?

firefox-beta Uplift Approval Request

  • User impact if declined: none
  • Code covered by automated testing: yes
  • Fix verified in Nightly: no
  • Needs manual QE test: no
  • Steps to reproduce for manual QE testing: n/a
  • Risk associated with taking this patch: none
  • Explanation of risk level: Adds tests for https://phabricator.services.mozilla.com/D254883
  • String changes made/needed: n/a
  • Is Android affected?: no
QA Whiteboard: [uplift][qa-triage-done-c142/b141]
Attachment #9496590 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Attachment #9496589 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Attachment #9496594 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Attachment #9496588 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Attachment #9496589 - Flags: approval-mozilla-beta+ → approval-mozilla-beta?
Attachment #9496589 - Attachment is obsolete: true
Attachment #9496589 - Flags: approval-mozilla-beta? → approval-mozilla-beta-
Attachment #9496593 - Attachment is obsolete: true
Attachment #9496593 - Flags: approval-mozilla-beta? → approval-mozilla-beta-
Attachment #9496592 - Attachment is obsolete: true
Attachment #9496592 - Flags: approval-mozilla-beta? → approval-mozilla-beta-
See Also: → 1978974

This enhancement was part of the work done on QA-4103 for which we already sent a testing report via email. Considering this, I am marking it as Verified - Fixed.

Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: