Closed Bug 1521615 Opened 2 years ago Closed 2 years ago

Top Sites header component usage

Categories

(Firefox :: New Tab Page, enhancement, P1)

enhancement

Tracking

()

VERIFIED FIXED
Firefox 66
Iteration:
66.4 - Jan 21 - 27
Tracking Status
firefox66 --- fixed

People

(Reporter: thecount, Assigned: thecount)

References

Details

(Keywords: github-merged)

Attachments

(1 file)

Right now topsites isn't providing a header, it has it in the comps.

To test:

  1. Ensure the new tab is the regular version by default.
  2. In about:config, change browser.newtabpage.activity-stream.discoverystream.config to be {"enabled":true,"layout_endpoint":"https://getpocket.com/v3/newtab/layout?version=1&consumer_key=40249-e88c401e1b1f2242d9e441c4&layout_variant=dev-test-all"}
  3. Ensure new tab is rendering components with readable headers for List, Hero, and top sites.
  4. Reset the pref, ensure everything is back to normal.
Assignee: nobody → sdowne
Iteration: --- → 66.4 - Jan 21 - 27
Priority: -- → P1
Blocks: 1521836
Status: NEW → RESOLVED
Closed: 2 years ago
Keywords: github-merged
Resolution: --- → FIXED
Target Milestone: --- → Firefox 66

QA Results:

Tested on :

FF Nightly version : 66.0a1 (2019-01-25)
OS : Mac and Windows 10 Pro

Results logged here (recording) :
https://www.dropbox.com/s/7vhh287pfj7sml2/QA%20Result%20%3A%20bug.%20-%201521615.mp4?dl=0
Closing as verified.

Status: RESOLVED → VERIFIED
Component: Activity Streams: Newtab → New Tab Page
You need to log in before you can comment on or make changes to this bug.