Bug 227705

Summary: Missing or Flickering Elements
Product: WebKit Reporter: Kerry <kerryliu>
Component: CompositingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: simon.fraser, zalan
Priority: P2    
Version: Safari Technology Preview   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Test case for flickering text
none
Test reduction
none
smfr testcase none

Description Kerry 2021-07-06 08:24:08 PDT
Created attachment 432933 [details]
Test case for flickering text

In the WordPress Block Editor, we were seeing elements flicker in Safari and the Safari Technology preview 127 in https://github.com/WordPress/gutenberg/issues/30803.

I've narrowed this down to a test case, which I've attached. It's also available at https://codepen.io/gwwar/pen/dyWYdmg

It should look like https://user-images.githubusercontent.com/1270189/124388676-c0a34f80-dc98-11eb-8987-aa0e6001c10c.mp4 with the bad behavior.

It's a little bit of a complex setup, requiring flex styles, an iframe, two fixed divs, and some z-index stacking contexts. We're are able to consistently reproduce this, so I do feel it's worthwhile to report. Let us know if folks have trouble reproducing or if y'all need more information. Thanks!
Comment 1 Kerry 2021-07-06 08:35:42 PDT
If it helps, there's also a few other videos available at https://github.com/WordPress/gutenberg/pull/32824#issuecomment-873280550 

Elements disappear or end up being ordered incorrectly when the iframe in .components-popover intersects with .block-editor-block-list__layout and causes a new compositing layer to be created.
Comment 2 zalan 2021-07-06 11:20:55 PDT
Created attachment 432947 [details]
Test reduction
Comment 3 Simon Fraser (smfr) 2021-07-06 12:31:53 PDT
Created attachment 432961 [details]
smfr testcase
Comment 4 Simon Fraser (smfr) 2021-07-06 14:39:42 PDT
Same as bug 220892, confirmed that the patch fixes it.

*** This bug has been marked as a duplicate of bug 220892 ***
Comment 5 Kerry 2021-07-07 07:58:26 PDT
Great to know this already had a patch fix! Thanks for looking into it.