microsoft / microsoft/fluentui

[Bug]: Fluent v9 Menu and Tooltip can detach from the anchor element when scrolling

Open
#25,100 20 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

Area: Positioning Component: Menu Fluent UI react-components (v9) Needs: Investigation Package: positioning Resolution: Soft Close
Dominant language
TypeScript
Stars
20.3k
Forks
2.9k
Avg merge
2d 9h
Merged PRs (30d)
46

Description

Library

React Components / v9 (@fluentui/react-components)

System Info
System:
    OS: Windows 10 10.0.22622
    CPU: (24) x64 12th Gen Intel(R) Core(TM) i9-12900KF
    Memory: 39.73 GB / 63.82 GB
  Browsers:
    Edge: Spartan (44.22621.586.0), Chromium (106.0.1370.34)
    Internet Explorer: 11.0.22621.1
Are you reporting Accessibility issue?

no

Reproduction

Ask chfalck

This codesandbox from behowell attempts to repro the conditions of the bug: https://codesandbox.io/s/pensive-bush-h5wixj?file=/example.tsx. It has a menu button inside a scrolling div, and a tooltip inside a scrolling menu. However, the bug doesn't seem to repro in this standalone scenario, so further investigation is needed to figure out what is different about the actual scenario.

Bug Description

Actual Behavior

Menus and tooltips can intermittently detach from their anchor elements when scrolling:

  1. Open a menu, or hover over an item with a tooltip
  2. Scroll with the mouse wheel

Result: the menu or tooltip don't follow their anchor.

Expected Behavior

Menu and Tooltip stay attached to their anchor while scrolling.

Logs

No response

Requested priority

Normal

Products/sites affected

No response

Are you willing to submit a PR to fix?

no

Validations
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • The provided reproduction is a minimal reproducible example of the bug.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.