Summary: | MaterialUI TextField + Dialog + resized Safari window results in DOM elements hiding when they shouldn't | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | bmueller.sykes | ||||||||
Component: | Compositing | Assignee: | Nobody <webkit-unassigned> | ||||||||
Status: | NEW --- | ||||||||||
Severity: | Normal | CC: | rniwa, simon.fraser, webkit-bug-importer, wenson_hsieh, zalan | ||||||||
Priority: | P2 | Keywords: | InRadar | ||||||||
Version: | Safari 12 | ||||||||||
Hardware: | Mac | ||||||||||
OS: | macOS 10.14 | ||||||||||
Attachments: |
|
Description
bmueller.sykes
2019-02-06 06:56:50 PST
I can't reproduce. Can you attach a screenshot of the broken appearance? Created attachment 361610 [details]
interlaced divs disappearing
Created attachment 361611 [details]
single div above Material-UI TextField components disappearing
Thanks for the reply! It's a bummer you guys can't reproduce. The MaterialUI guys couldn't either, but I'm not imagining things. I've seen this behavior on 3 different machines now (the one I'm currently using is Version 12.0.3 (13606.4.5.3.1)). I have absolutely no idea why it's exhibiting this behavior for me, but not you or the MaterialUI people. Frustrating, obviously. None of the Safari instances have extensions. I'd be happy to send over a full list of settings/config for my instance of Safari, but I don't know how to get a dump of that. I can reproduce now. This looks like a compositing bug. To work around it, put z-index:0 on <div class="MuiPaper-root-19 MuiPaper-elevation24-45 MuiPaper-rounded-20 MuiDialog-paper-5 MuiDialog-paperScrollPaper-6"> Created attachment 361624 [details]
Standalone testcase
Thank you for your investigation and your replies. The "standalone test case" still breaks for me--I'm assuming that is as designed, correct? When you say this is a "composition bug", is that a bug with Material-UI's code, or with the Safari rendering engine? I ask because this bug appears to be unique to Safari (it doesn't break in Chrome, which has the most similar rendering engine). I'm happy to circle back with the Material-UI team with your findings, but I want to be clear about what I'm saying. Thanks again!! It's a WebKit bug. Okay, great! Thanks! What's the timeline for something like this to get fixed and find its way into a production build of Safari? Just trying to set my own expectations. |