> Another section of the application that displays important user data is completely hidden because of a drop shadow.

Clarification: It starts out visible, but then becomes invisible after the list becomes long enough that a scrollbar is displayed.

Doesn't reproduce for me with Version 65.0.3325.106 on Retina 10.13, nor on Canary.

Do you have any other machine to test on?

As it seems likely to be a GPU issue, please navigate to chrome://gpu and paste or attach the contents here.

Thanks for the quick reply! Here's my chrome://gpu: https://docs.google.com/document/d/1AdMvi05P2r3Ksd4MN9toaSbFc9SXQfO0xFadtVAYILo/edit

I just tested, and I can't reproduce the issue on my Android phone running Chrome 65 either. The BrowserStack testing I mentioned was in Chrome 65 on both macOS High Sierra and OS X El Capitan.

Thanks for filing the issue!

Checked the issue on reported chrome version 65.0.3325.162 using Mac 10.13.1 with the below mentioned steps.
1. Launched Chrome
2. Navigated to https://cyph.ws
Even after trying many times it says "Loading Cyph failed. Please try again later." Attaching the screen cast of the same.

@Reporter: Could you please have a look at the screen cast and please provide any other information(Other URL-if any) which helps us to triage the issue in a better way.

Deleted: 821876.mp4 6.4 MB

	821876.mp4 6.4 MB View Download

Hmm, thanks for the report! I'm not able to reproduce the issue, but that's very concerning. Could a local firewall or something be the culprit?

As far as an alternate test URL: https://plnkr.co/edit/wCI99L4FqFRSUh2L34mF?p=preview

We managed to reproduce this issue using Chrome 65 on BrowserStack after cycling through a few instances of OS X El Capitan; see attached chrome://gpu output.

Deleted: JvB4WyyW.txt 9.9 KB

JvB4WyyW.txt 9.9 KB View Download

We're seeing this issue too. We had a client report it on Mac OS 10.11.6 with Chrome 65.0.3325.162, and today two engineers at our company showed me their screens with this occurring. Notably, both of the folks in my office were using previous-gen Macbook Pros (not the new thinner ones with the touchbar). I created a test page that consistently displays incorrectly for them in Chrome:

https://hiplung.com/drop-shadow-test/

I first tried just the `filter: drop-shadow(...)` style, but that didn't cause the issue by itself. Adding a `transform: translateZ(0px)` to the style was able to force the issue to happen though (presumably since this forces the div into its own compositing layer or own GPU texture or whatever).

I'm attaching the results of chrome://gpu for the two Macs in my office that were displaying this error.

Deleted: chrome_gpu_error_0.txt 9.6 KB

chrome_gpu_error_0.txt 9.6 KB View Download

Deleted: chrome_gpu_error_1.txt 9.9 KB

chrome_gpu_error_1.txt 9.9 KB View Download

Just asked my coworker who's Mac was showing the issue to screenshot my test page so I could paste the broken image in here, and it was actually working correctly for him. I asked him to unplug his external monitor, and then Chrome showed the issue. I think his Mac might switch from the more powerful GPU to the integrated Intel GPU when you unplug an external monitor. Maybe that's a useful bit of info. In any case, I'm attaching the image of the broken state of the test page (https://hiplung.com/drop-shadow-test/)

Deleted: Screen Shot 2018-03-20 at 5.27.58 PM.png 74.1 KB

	Screen Shot 2018-03-20 at 5.27.58 PM.png 74.1 KB View Download

Two other things that I'd guess have the same root cause:

1. filter: hue-rotate combined with brightness and/or saturate causes the target to disappear.

2. Attached is what it looks like when I mouse over a link in the JS console.

Deleted: Screen Shot 2018-03-28 at 10.09.15 PM.png 24.5 KB

	Screen Shot 2018-03-28 at 10.09.15 PM.png 24.5 KB View Download

Mac triage: marking for Blink>CSS triage.

Mac specific compositing issue? Not paint, CSS or Layout if it only occurs on some Mac machines.

Currently we do not have Mac 10.11.6 so tried checking the issue using a cloud-based cross-browser testing tool(https://www.browserstack.com/).
Able to reproduce this issue on browserstack  using Mac OS 10.11.6
However unable to bisect this as we don't have access to other builds there.

Thanks!

As per comment# 14, the issue seems to be specific to Mac 10.11, hence adding 'Mac-10.11' label to this issue.

Thanks!

Could anyone from MTV check this and help in getting this tested on Mac OS 10.11 if it can be arranged.

I don't think this is isolated to MacOS 10.11. If you'll see my comment #8, I attached two dumps of chrome://gpu from two different machines at my office that were exhibiting this issue. One is running 10.11.6 and the other is running 10.10.5.

I also noted in comment #9 that switching from the discrete GPU in the macbook pro to the integrated Intel GPU seemed to cause this problem -- everything looked fine with the discrete GPU, and then after unplugging an external monitor (causing the mac to switch to integrated GPU) the rendering issue appeared.

Looking at those chrome://gpu dumps (attached to comment #8) a bit more, I see these lines in both of them, which looks pretty ominous:

 Problems Detected  
 Rendering artifacts on older macOS releases and Intel GPUs: 794819

Is this bug a duplicate of this? https://bugs.chromium.org/p/chromium/issues/detail?id=794819

Has this been fixed? Doesn't seem like I can reproduce it anymore in Chrome 68 (same OS X version and everything else as in my original report).