Material-UI 4: popover loose positioning
See original GitHub issueWe are using Gatsbyjs and switched out React with Preact X. Everything works fine, except all the popover loose their positioning and open in the top let corner (x: 0, y:0).
preact@10.2.1
@material-ui/core@4.8.3
@material-ui/styles@^4.8.2
As I haven’t found any information, that would suggest, that these wouldn’t work with Preact.
===
Edit: Added an Example.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:9
- Comments:29 (11 by maintainers)
Top Results From Across the Web
material UI popover - position on small screen - Stack Overflow
I have been trying for some time to figure out a way to position material ui popover under my anchor, and leave it...
Read more >Popover API - Material UI - MUI
Name Type Default
open * bool false
action ref
anchorEl HTML element | func
Read more >@material-ui/core | Yarn - Package Manager
Fast, reliable, and secure dependency management.
Read more >Fix header in scrolling material-ui popover - Stack Overflow
I can achieve the desired result by setting a simple style={{ height: 250 }} on Content , but then I'd lose the dynamic...
Read more >React Material-UI Cookbook - Open Directory Data Archive
I would like to thank all Material-UI's contributors for their devotion to ... using fixed positioning, AppBar components remain visible even as the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@JoviDeCroock you’re a legend! 💪 thanks for all the effort to make this happen.
I identified the issue, this seems to be a regression in 4.8.2 --> 4.8.3 related to Preact. We’ll have to see in what sense we handle the following scenario differently: https://github.com/mui-org/material-ui/pull/19046/files
I’d assume our function is called too late