Closed Bug 1625958 Opened 5 months ago Closed 4 months ago

The "Breached Website" and the "Vulnerable Passwords" notifications are not displayed below the header

Categories

(Firefox :: about:logins, defect, P1)

Desktop
All
defect

Tracking

()

VERIFIED FIXED
Firefox 76
Tracking Status
firefox76 --- verified

People

(Reporter: srosu, Assigned: jaws)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

[Affected versions]:

  • Nightly 76.0a1 (Build ID: 20200330094747)

[Affected Platforms]:

  • Windows 10 x64
  • Mac 10.14.6
  • Ubuntu 18.04 x64

[Prerequisites]:

  • Have a profile with at least 3 saved logins in which one is vulnerable.

[Steps to reproduce]:

  1. Open the Firefox browser with the profile from prerequisites
  2. Select a vulnerable login.
  3. Observe the top part of the Login view.

[Expected result]:

  • The “Vulnerable Password” notification is displayed below the header.

[Actual result]:

  • The “Vulnerable Password” notification is displayed above the header.

[Notes]:

  • Based on the mock-ups, the "Breached Website" and the "Vulnerable Passwords" notifications should be displayed under the header (under the website, “Edit” and “Remove” buttons.
  • The issue is also reproducible on older Firefox versions with the old breached notification.
  • Attached a screenshot of the issue.
Assignee: nobody → jaws
Status: NEW → ASSIGNED
Priority: -- → P1
Pushed by jwein@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5c7791ca479d
Move the breach alert and vulnerable password alert beneath the header. r=MattN
Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 76

I have verified this issue using the latest Nightly 76.0a1 (Build ID: 20200401095134) on Windows 10 x64, Mac 10.14, Ubuntu 18.04 x64.

  • The "Breached Website" and the "Vulnerable Passwords" notifications are correctly displayed below the header.
Status: RESOLVED → VERIFIED
No longer regressions: 1626627
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.