[Popover] Falling offscreen, doesn't reposition without window.resize event

[ntbosscher]

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Current behavior 😯

Popover is partially offscreen until a window.resize event is triggered.

Expected behavior 🤔

Should automatically stay within the window bounds.

Steps to reproduce 🕹

https://codesandbox.io/s/modern-grass-x8043b

Context 🔦

I'm trying to build a user info menu on an AppBar header

Your environment 🌎

`npx @mui/envinfo`

Running on Mac: Chrome Version 101.0.4951.54 (Official Build) (x86_64)

  Output from `npx @mui/envinfo` goes here.
  System:
    OS: macOS 12.3.1
  Binaries:
    Node: 16.14.0 - ~/.nvm/versions/node/v16.14.0/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 8.3.1 - ~/.nvm/versions/node/v16.14.0/bin/npm
  Browsers:
    Chrome: 101.0.4951.54
    Edge: 95.0.1020.44
    Firefox: 99.0.1
    Safari: 15.4
  npmPackages:
    @emotion/react: ^11.9.0 => 11.9.0 
    @emotion/styled: ^11.8.1 => 11.8.1 
    @mui/base:  5.0.0-alpha.79 
    @mui/icons-material: ^5.6.2 => 5.6.2 
    @mui/material: ^5.6.4 => 5.6.4 
    @mui/private-theming:  5.6.2 
    @mui/styled-engine:  5.6.1 
    @mui/system:  5.6.4 
    @mui/types:  7.1.3 
    @mui/utils:  5.6.1 
    @types/react: ^18.0.0 => 18.0.8 
    react: ^18.1.0 => 18.1.0 
    react-dom: ^18.1.0 => 18.1.0 
    typescript: ^4.4.2 => 4.6.4 

[ntbosscher]

[ntbosscher]

Possibly related to: #10595
The difference is that I would expect the Popover to handle the repositioning on it's own when the rendering isn't deferred/updated after the initial open.

[siriwatknp]

It works correctly in my machine.

Screen.Recording.2565-05-31.at.12.16.03.mov

[ntbosscher]

Interesting... I assume you're testing on the latest stable release of Chrome?

…

On Tue., May 31, 2022, 1:16 a.m. Siriwat K, ***@***.***> wrote: It works correctly in my machine. https://user-images.githubusercontent.com/18292247/171097955-6b9a2241-d789-4a67-9c80-7fa9fa707db9.mov — Reply to this email directly, view it on GitHub <#32704 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAS7GZ6TRP4JSNK3OEXUCMLVMWODRANCNFSM5VPFRDSA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[siriwatknp]

@ntbosscher I believe it is (Version 102.0.5005.61 (Official Build) (arm64))

[ntbosscher]

Thank you @siriwatknp! Your response got me digging a bit further.

Looks like the problem is caused by a Font Fingerprint extension I had turned on.

Definitely out of the scope of this project. Thank you all for your help!