RESOLVED CONFIGURATION CHANGED 188627
STP: Google Maps sidebar renders black 
https://bugs.webkit.org/show_bug.cgi?id=188627
Summary STP: Google Maps sidebar renders black
Jon
Reported 2018-08-15 19:29:25 PDT
Created attachment 347236 [details] Shot of Google Maps with black sidebar. Loading maps.google.com initially renders the sidebar fine but it flashes to black after a second. Search field seems to work, but content renders black again. Tried loading without 1Blocker, same result. Only other plugin is 1Password. 10.13.6, STP 63. This has been occurring for the last few STP builds. See attached screen shot.
Attachments
Shot of Google Maps with black sidebar. (2.94 MB, image/png)
2018-08-15 19:29 PDT, Jon 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2018-08-15 22:49:32 PDT
<rdar://problem/43366811>
Simon Fraser (smfr)
Comment 2 2018-10-31 13:26:20 PDT
*** Bug 191082 has been marked as a duplicate of this bug. ***
Simon Fraser (smfr)
Comment 3 2018-10-31 13:27:10 PDT
Supposedly fixed by r235843.
Simon Fraser (smfr)
Comment 4 2018-10-31 13:28:10 PDT
But that was over a month ago, and we still have reports coming from more recent STP builds.
Jon
Comment 5 2018-10-31 14:08:47 PDT
Seems fixed in STP 68, at least for me.
Jon
Comment 6 2018-10-31 14:09:43 PDT
That would be STP 68 on 10.14.1.
Ryosuke Niwa
Comment 7 2018-11-02 03:34:44 PDT
This is definitely broken on STP68 for me. Maybe we need high sierra or MacBookPro10,1 to reproduce it?
Simon Fraser (smfr)
Comment 8 2018-11-02 09:59:57 PDT
<rdar://problem/45685714>
Ryosuke Niwa
Comment 9 2018-11-06 10:22:02 PST
Hm... I'm not reproducing this problem on the same machine either. It's possible this is some kind of a GPU driver bug in MacBookPro10,1.
Simon Fraser (smfr)
Comment 10 2018-11-07 10:53:35 PST
It's not a rendering issue; the element background really is black. It's about the timing of the sidebar rolling up.
Ryosuke Niwa
Comment 11 2019-07-04 02:10:27 PDT
I haven't seen this in a while. I suspect the website has fixed the issue.
Note You need to log in before you can comment on or make changes to this bug.