Closed Bug 1529530 Opened 6 years ago Closed 5 years ago

[Scroll anchoring] Keyboard navigation is not working properly with the browser’s width considerable reduced

Categories

(Core :: Layout: Scrolling and Overflow, defect, P3)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1554572
Tracking Status
firefox65 --- unaffected
firefox66 --- fix-optional
firefox67 --- fix-optional
firefox68 --- wontfix

People

(Reporter: asoncutean, Unassigned)

References

Details

(Keywords: regression)

[Affected versions]:

  • 66.0b9
  • 66.0a1 (2019-02-20)

[Affected platforms]:

  • Win 10 x64
  • Ubuntu 18 x64
  • macOS 10.13

[Steps to reproduce]:

  1. Go to https://forum.gaijinpot.com/forum/community-center/general-discussion
  2. Reduce the width of the browser to or less than 497px
  3. Scroll the page using the navigation keyboards or the up-down arrow buttons on the scrollbar.

[Expected result]:

  • Scrolling is performed smoothly.

[Actual result]:

  • Scrolling action is barely noticeable.

[Regression range]:

[Additional Notes]:

  • With the layout.css.scroll-anchoring.enabled on false, this issue is not reproducible.
Has Regression Range: --- → yes

I see the same bad results in Chrome, too. So this seems likely to be a legitimate interaction issue caused by the Scroll Anchoring feature, regardless of browser.

rhunt, perhaps you could take a look at what's causing trouble here & whether there's anything obvious we could fix to avoid it?

Flags: needinfo?(rhunt)
Priority: -- → P3

Bulk change to wontfix for 68 (P3+ carryover with needinfo).

I won't have time to look at this anytime soon, unfortunately.

Flags: needinfo?(rhunt)

I think this is fixed now, mind confirming?

Flags: needinfo?(anca.soncutean)

This issue is no longer reproducible with the latest Nightly 70.0a1 (2019-07-25) and Beta 69.0b8 on Windows 10, macOS 10.13 and Ubuntu 18.04.

Flags: needinfo?(anca.soncutean)
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.