Closed Bug 1974269 Opened 7 months ago Closed 6 months ago

The Pinned icon is not displayed on the selected state when opening the Shortcut menu with Space or Enter keys

Categories

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

Desktop
Unspecified
defect

Tracking

()

VERIFIED FIXED
143 Branch
Accessibility Severity s3
Tracking Status
firefox-esr128 --- disabled
firefox-esr140 --- disabled
firefox140 --- disabled
firefox141 --- verified
firefox142 --- verified
firefox143 --- verified

People

(Reporter: rdoghi, Assigned: amy)

References

Details

(Keywords: access, Whiteboard: [hnt])

Attachments

(4 files)

Attached image 2025-06-26_14h57_19.png

Found in

  • Nightly 142.0a1 (2025-06-26)

Affected versions

  • Nightly 142.0a1 (2025-06-26)
  • Beta 141.0b2

Affected platforms

  • all

Steps to reproduce

  1. Open the New Tab Page and pin a few shortcuts.
  2. Reach Any Shortcut from the new tab page using keyboard navigation.
  3. Reach the Shortcut menu and open it using the Space or Enter keys.

Expected result

  • The pinned icon should be displayed for that selected state since the shortcut is pinned.

Actual result

  • There is no indication that the shortcut is pinned if the user reachs the shortcut with keyboard navigation.
    If the user opens the shortcut Menu using keyboard navigation the pin icon is not displayed for that selected state.
    Only indication of the shortcut being pinned is the "Unpin" option.

Please note that in older builds before this feature the pinned icon was always displayed on the Top site.

Regression range
Not Applicable

Assignee: nobody → achurchwell
Whiteboard: [hnt]

The severity field is not set for this bug.
:thecount, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(sdowne)
Severity: -- → S2
Priority: -- → P1
Flags: needinfo?(sdowne)
Attachment #9499912 - Attachment description: Bug 1974269 – topsites pinned icon is not displayed on focus or read to screen readers. r=#home-newtab-reviewers → Bug 1974269 – topsites pinned icon is not displayed on focus. r=#home-newtab-reviewers
Pushed by achurchwell@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/70c73d50f502 https://hg.mozilla.org/integration/autoland/rev/85d0f226d532 – topsites pinned icon is not displayed on focus. r=home-newtab-reviewers,reemhamz
Attachment #9502513 - Flags: approval-mozilla-beta?

firefox-beta Uplift Approval Request

  • User impact if declined: Accessibility users can not see pinned icon when navigating topsites with keyboard.
  • Code covered by automated testing: yes
  • Fix verified in Nightly: no
  • Needs manual QE test: yes
  • Steps to reproduce for manual QE testing: Steps to test are in original bugzilla bug
  • Risk associated with taking this patch: Low
  • Explanation of risk level: Styles only patch
  • String changes made/needed: N/A
  • Is Android affected?: no
Flags: qe-verify+
Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → FIXED
Target Milestone: --- → 143 Branch

Verified as fixed in our latest Nightly 143.0a1 (2025-07-23)

Attachment #9502513 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
QA Whiteboard: [qa-found-in-c141][QA-4106] → [qa-found-in-c141][QA-4106][qa-ver-needed-c143/b142]
QA Contact: rdoghi
QA Whiteboard: [qa-found-in-c141][QA-4106][qa-ver-needed-c143/b142] → [qa-found-in-c141][QA-4106][uplift][qa-ver-needed-c143/b142]

Verified as fixed in our latest Beta 142.0b3

Accessibility Severity: --- → s3
Keywords: access
Attachment #9503190 - Flags: approval-mozilla-release?

firefox-release Uplift Approval Request

  • User impact if declined: User impact to a11y
  • Code covered by automated testing: yes
  • Fix verified in Nightly: no
  • Needs manual QE test: yes
  • Steps to reproduce for manual QE testing: Steps to test in bugzilla
  • Risk associated with taking this patch: Low
  • Explanation of risk level: It's some css for opacity on hover
  • String changes made/needed: None
  • Is Android affected?: no
Attachment #9503190 - Flags: approval-mozilla-release? → approval-mozilla-release+

This issue is verified as fixed in our latest Release 141.0.1

Status: RESOLVED → VERIFIED
QA Whiteboard: [qa-found-in-c141][QA-4106][uplift][qa-ver-needed-c143/b142] → [qa-found-in-c141][QA-4106][uplift][qa-ver-done-c143/b142]
Flags: qe-verify+

Downgrading to S3 as it fits more our user impact definition (https://wiki.mozilla.org/BMO/UserGuide/BugFields#bug_severity) and we also set it as access-S3

Severity: S2 → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: