Bug 194342 - MaterialUI TextField + Dialog + resized Safari window results in DOM elements hiding when they shouldn't
Summary: MaterialUI TextField + Dialog + resized Safari window results in DOM elements...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Compositing (show other bugs)
Version: Safari 12
Hardware: Mac macOS 10.14
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2019-02-06 06:56 PST by bmueller.sykes
Modified: 2019-02-11 07:13 PST (History)
5 users (show)

See Also:


Attachments
interlaced divs disappearing (2.53 MB, image/gif)
2019-02-09 14:07 PST, bmueller.sykes
no flags Details
single div above Material-UI TextField components disappearing (2.77 MB, image/gif)
2019-02-09 14:08 PST, bmueller.sykes
no flags Details
Standalone testcase (8.35 KB, text/html)
2019-02-09 22:59 PST, Simon Fraser (smfr)
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description bmueller.sykes 2019-02-06 06:56:50 PST
I opened a ticket for this over at Material UI's GitHub page here (including screen captures of the problem):

https://github.com/mui-org/material-ui/issues/14411

...and produced a Codesandbox here:

https://8222owpkq9.codesandbox.io

The problem is that when Material UI TextField (React) components are within a Material UI Dialog component, when the browser is shrunk vertically, elements that are *not* TextField components (e.g. just generic divs or whatever) are partially or entirely obscured by...something. Looking at the web inspector, at the moment when the items disappear, I don't see any updates to the inspector indicating CSS or DOM elements have been added or removed. It might well be some sort of z-index issue, but I can't pin it down. It does not appear to be the case that the disappearing items move to the left or right

The Material UI maintainers weren't willing or able to help, in part because this problem is not replicable all of the time. In limited testing in my office, we reproduced it on about 75% of machines running Safari. Of course the Material UI maintainers were not able to reproduce it, so they couldn't track it down.

I think this is a relatively recent issue, because it's prominent enough, and enough of my team uses Safari in development, that I think we would have noticed it before now.

Thanks in advance!
Comment 1 Simon Fraser (smfr) 2019-02-08 19:42:32 PST
I can't reproduce. Can you attach a screenshot of the broken appearance?
Comment 2 bmueller.sykes 2019-02-09 14:07:43 PST
Created attachment 361610 [details]
interlaced divs disappearing
Comment 3 bmueller.sykes 2019-02-09 14:08:45 PST
Created attachment 361611 [details]
single div above Material-UI TextField components disappearing
Comment 4 bmueller.sykes 2019-02-09 14:11:31 PST
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.
Comment 5 Simon Fraser (smfr) 2019-02-09 22:09:43 PST
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">
Comment 6 Radar WebKit Bug Importer 2019-02-09 22:10:42 PST
<rdar://problem/47946563>
Comment 7 Simon Fraser (smfr) 2019-02-09 22:59:25 PST
Created attachment 361624 [details]
Standalone testcase
Comment 8 bmueller.sykes 2019-02-10 12:36:27 PST
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!!
Comment 9 Simon Fraser (smfr) 2019-02-10 20:20:21 PST
It's a WebKit bug.
Comment 10 bmueller.sykes 2019-02-11 07:13:09 PST
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.