1401254 - The favicons on the New Tab Page overlap the snippets section

Status: VERIFIED FIXED

(Firefox :: New Tab Page, defect)

Description

[Jared Wein [:jaws] (please needinfo? me)]

Attachment: Screenshot of bug

See attached screenshot.

To reproduce, open a new window and resize the window to not be that tall. Open a new tab and you will see the favicons appear on top of the snippets section.

Comment 1

[Ed Lee :Mardak]

Fixed by https://github.com/mozilla/activity-stream/pull/3524 to be uplifted via bug 1401683.

Comment 2

[Iulia Cristescu, QA [:JuliaC] (away, please needinfo? [e-mail])]

I wasn't able to reproduce the initial issue on 57.0a1 (2017-09-19) using Windows 10 x64 and macOS 10.13, based on the details from comment 0 (here is the behavior screencast https://goo.gl/xL7s3m). Yet, the issue is not reproducible neither on 57.0b7 (20171009192146), across above mentioned platforms. 
Jared, am I missing something?

Comment 3

[Ed Lee :Mardak]

Iulia, sorry for the confusing "snippets". There's two types of snippets. Your screencast is showing Onboarding's notification (notice the [x] on the right) whereas jaws' screenshot is of the remote snippets service's snippet (no [x]). And I don't know offhand how to get the remote snippets service to show something because there might not be a snippet being served right now.

Comment 4

[Iulia Cristescu, QA [:JuliaC] (away, please needinfo? [e-mail])]

(In reply to Ed Lee :Mardak from comment #3)
> Iulia, sorry for the confusing "snippets". There's two types of snippets.
> Your screencast is showing Onboarding's notification (notice the [x] on the
> right) whereas jaws' screenshot is of the remote snippets service's snippet
> (no [x]). And I don't know offhand how to get the remote snippets service to
> show something because there might not be a snippet being served right now.

Thank you for the clarification! I will keep monitoring this, to verify the fix when the remote snippets will be again displayed. Also, if there is another way I can verify it, please let me know! 
I'll leave a ni for myself.

Comment 5

[Iulia Cristescu, QA [:JuliaC] (away, please needinfo? [e-mail])]

Managed to reproduce the initial issue on 57.0a1 (2017-09-19). I can confirm that 57.0b12 (20171026211016) build is verified fixed, using Windows 10 x64, Ubuntu 16.04 x64 and macOS 10.13.