1555953 - Inconsistent hover behavior for borderless cards and various components

Status: RESOLVED WORKSFORME

(Firefox :: New Tab Page, defect, P3)

Description

[Marius Coman [:mcoman], Ecosystem QA]

Attachment: rec of the issue.gif

[Affected versions]:

• Firefox Beta 68.0b5, Build ID 20190527103257
• Firefox Nightly 69.0a1, Build ID 20190530214830

[Affected Platforms]:

• All Windows
• All Linux
• All Mac

[Prerequisites]:

• Have the folowing prefs in the "about:config" page:
  • "browser.search.region" set to "US"
  • "browser.newtabpage.activity-stream.discoverystream.config" set to "{"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":false,"layout_endpoint":"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=40249-e88c401e1b1f2242d9e441c4&layout_variant=dev-test-all"}"

[Steps to reproduce]:

1. Open the browser with the profile from prerequisites.
2. Open a new tab and hover a card without borders.
3. Observe the behavior.

[Expected result]:

• The card's title is highlighted in blue.

[Actual result]:

• A grey outline is also displayed around the card.

[Regression window]:

• Considering the fact that this issue is not reproducible with the Firefox Nightly build from 03/20/2019, using the Mozregression tool, I have managed to find a regression window:
  Last good revision: 8e8ea33ecb3da138dbd0af56c2e5550902e7b05a
  First bad revision: f78634b8bff9ce0b8850e5f9246e7821ded4ef4e
  Pushlog:
  https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=8e8ea33ecb3da138dbd0af56c2e5550902e7b05a&tochange=f78634b8bff9ce0b8850e5f9246e7821ded4ef4e

[Notes]:

• This issue is not reproducible with the "Hero" element or with the borderless lists.
• Attached a screen recording of the issue.

Comment 1

[Marius Coman [:mcoman], Ecosystem QA]

Ed, could you please take a look over this?

Comment 2

[Ed Lee :Mardak]

Bug 1548995 is covering specifically the gray outline spacing for borderless cards, but I don't think there's a general hover inconsistency bug, so morphing this one.

Comment 3

[Jessilyn Davis]

This experience won't be going live with the winning layout. Moving this to Backlog if/when we think about responsive and next layout configs.

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

The component has been changed since the priority was decided, so we're resetting it.
For more information, please visit auto_nag documentation.

Comment 5

[Petruta Horea [:phorea], Desktop Test Engineering (back on Sep 5th)]

The described behavior is no longer reproducible in latest Nightly 91.0a1 under Win 10 64-bit, so closing as RWFM.