Closed Bug 1849558 Opened 10 months ago Closed 7 months ago

Firefox view navigation list items have the focus ring cut

Categories

(Firefox :: Firefox View, defect, P3)

Firefox 118
Desktop
All
defect

Tracking

()

VERIFIED FIXED
121 Branch
Tracking Status
firefox-esr102 --- unaffected
firefox-esr115 --- unaffected
firefox116 --- unaffected
firefox117 --- unaffected
firefox118 --- disabled
firefox119 --- wontfix
firefox120 --- wontfix
firefox121 --- fixed

People

(Reporter: csasca, Assigned: nsharpley)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: regression, Whiteboard: [fidefe-firefox-view])

Attachments

(2 files)

Attached image fx view focus ring .png

Found in

  • Firefox 118.0a1

Affected versions

  • Firefox 118.0a1

Tested platforms

  • Affected platforms: macOS 13.5, Ubuntu 22.04, Windows 10

Preconditions

  • browser.tabs.firefox-view-next is set to true

Steps to reproduce

  1. Launch Firefox and access Firefox View
  2. Tab between the categories on the left side of the page

Expected result

  • The focus ring is not cut

Actual result

  • The focus ring is cut on both left and right sides

Regression range

  • Mozregression points that this was introduced by: Bug 1849195 - Use max-width/height to prevent extra scrollbars. r=dholbert,fxview-reviewers,kcochrane

Additional notes

  • The issue can be seen in the attachment

Set release status flags based on info from the regressing bug 1849195

:mkaply, since you are the author of the regressor, bug 1849195, could you take a look?

For more information, please visit BugBot documentation.

Flags: needinfo?(mozilla)

Set release status flags based on info from the regressing bug 1849195

OS: macOS → All
Priority: -- → P3

minor issue but keep fx120 affected given that Firefox View will be enabled in 119

(In reply to Dianna Smith [:diannaS] from comment #3)

minor issue but keep fx120 affected given that Firefox View will be enabled in 119

Hi, is there a reason we want to track this for 120 given that its an S4? Is it because its a regression?

We are not tracking per say (that would have a tracking +) , but just marked the status flag as affected so that it continues to show up in our queries. It is a recent minor regression for a feature that is about to be enabled. If you prefer for it to be out of sight, i dont mind either way. :)

Removed the overflow property to prevent focus ring from being clipped.

Assignee: nobody → nsharpley
Status: NEW → ASSIGNED
Attachment #9362673 - Attachment description: WIP: Bug 1849558 Firefox View navigation focus ring visibility → Bug 1849558 Firefox View navigation focus ring visibility
Attachment #9362673 - Attachment description: Bug 1849558 Firefox View navigation focus ring visibility → WIP: Bug 1849558 Firefox View navigation focus ring visibility
Attachment #9362673 - Attachment description: WIP: Bug 1849558 Firefox View navigation focus ring visibility → Bug 1849558 Firefox View navigation focus ring visibility
Attachment #9362673 - Attachment description: Bug 1849558 Firefox View navigation focus ring visibility → Bug 1849558 Fix Firefox View navigation focus ring visibility
Pushed by sfoster@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/3a79628380eb
Fix Firefox View navigation focus ring visibility r=fxview-reviewers,sfoster
Status: ASSIGNED → RESOLVED
Closed: 7 months ago
Resolution: --- → FIXED
Target Milestone: --- → 121 Branch

Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.

The patch landed in nightly and beta is affected.
:nsharpley, is this bug important enough to require an uplift?

  • If yes, please nominate the patch for beta approval.
  • If no, please set status-firefox120 to wontfix.

For more information, please visit BugBot documentation.

Flags: needinfo?(nsharpley)
Flags: needinfo?(nsharpley)
Flags: qe-verify+

Reproduced the issue with Firefox 118.0a1 (2023-08-21) on macOS 12 ARM.
The issue is verified fixed with Firefox 122.0a1 (20231127214936) and Firefox 121.0b4 (20231127091758) on macOS 12 ARM, Ubuntu 22.04 and Win 10.

Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: