Affected versions

• 75.0, 76.0b7, 77.0a1 (2020-04-21);

Affected platforms

• macOS 10.15.3, Windows 10, Ubuntu 18.04;

Steps to reproduce

1. Launch Firefox, save/set up at least 2 accounts for any webpage;
2. Access that webpage, click to open the saved login options;
3. Hover over the logins;

Expected result

• hover effect applied over the on-hover element;

Actual result

• login data not marked as hovered over, as per Saved Logins button;

Regression range

• First bad: 2019-07-18;
• Last good: 2019-07-17;
• Pushlog: URL
• not a regression, with introduction of the new about:logins page; checked after that and considered builds prior to it as good. With introduction of it, the hover was not implemented on it at all.

Additional notes

• attaching screenshot with the "affected area".

Is this with the default theme or a dark theme? It sounds like this is specific to dark mode.

Indeed, the hover effect appears on the Light Theme setup.

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

Hey Matt, It's me again, could I be assigned for this one as well?

Depends on D76468

I think I messed up, need your help please... this commit bug fix does NOT depend on D76468, tried to solve it myself but i couldn't

(In reply to f94olivera from comment #4)

Hey Matt, It's me again, could I be assigned for this one as well?

Attaching a patch assigns you automatically

(In reply to f94olivera from comment #6)

I think I messed up, need your help please... this commit bug fix does NOT depend on D76468, tried to solve it myself but i couldn't

Fixed.

I commented on the bug that I'm not sure this is the right solution as it also changes outside of the dark theme but doesn't cleanup the existing styles.

The bug assignee didn't login in Bugzilla in the last 7 months.
:sgalich, could you have a look please?
For more information, please visit auto_nag documentation.

Hey all, thank you for filing and working on this bug.
I just tested on Firefox 100 and the issue does not exists anymore, closing this bug and patch as WORKSFORME.