Adding release blocker label for this issue.Please reduce priority or remove if not the case.

Thank You!

Thank you for the report!

Some reason i'm not seeing this issue on Lenovo (YOGA 710-11IKB) Win10 touch laptop for the reported chrome version#66.0.3359.117.

avshaikh@, can you please double check by resetting all chrome://flags? or on any other Win10 touch device? 

This shouldn't block M66 stable and i'm punting this to M67.

Hi,

Tried resetting all flags from chrome://flags page in reported chrome build #66.0.3359.117 and issue can still be reproduced with all flags reset. Currently we are using Dell (Inspiron 15R) Win-10 touch machine to reproduce this issue.

Note : 
1. Able to repro issue in todays Dev #67.0.3396.10 build as well.
2. Tried re-bisecting and got the same revision again.

Thank you..!!

Thank you for checking. This seems to be hardware/gpu specific and will try to see if i find the same configuration.

I found what might have caused the issue. I'll be reverting the change and then maybe you could test it again on the canary once its available? We do not have the necessary hardware to test that out right now on our end.

The change pointed to could not have possibly caused the issue by the way, but this one could maybe have done it: 
https://chromium.googlesource.com/angle/angle.git/+/c0db9addeaebc76c7cc99b26aa27df5e432097ac%5E%21/#F0

avshaikh@, could you also please join a screenshot of the chrome://gpu screen on the device you are able to repro the issue with? 

The following revision refers to this bug:
  https://chromium.googlesource.com/angle/angle/+/1d97a4d0363da16a8d3ed942c515c0f738ed74e8

commit 1d97a4d0363da16a8d3ed942c515c0f738ed74e8
Author: Luc Ferron <lucferron@chromium.org>
Date: Thu Apr 19 12:15:30 2018

Revert "Fix dEQP renderbuffer unspecified attachment test."

This seems to have caused a regression in Chrome. I'm reverting the
change and suppressing the test that is failing on our end because of
it. Once we can confirm this solves the problem, we'll need some help
investigating further.

This reverts commit c0db9addeaebc76c7cc99b26aa27df5e432097ac.

Bug: angleproject:2321
Bug:  chromium:833809 
Change-Id: I5e40364217e15ae6117f5288a4754b25d983ca0a
Reviewed-on: https://chromium-review.googlesource.com/1017763
Commit-Queue: Luc Ferron <lucferron@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>

[modify] https://crrev.com/1d97a4d0363da16a8d3ed942c515c0f738ed74e8/src/tests/deqp_support/deqp_gles3_test_expectations.txt
[modify] https://crrev.com/1d97a4d0363da16a8d3ed942c515c0f738ed74e8/src/libANGLE/FramebufferAttachment.cpp

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/4abe7b0fa63ea44106468ac4e0a5d67c3dd33c22

commit 4abe7b0fa63ea44106468ac4e0a5d67c3dd33c22
Author: angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Thu Apr 19 14:30:32 2018

Roll src/third_party/angle/ eeec3b14c..1d97a4d03 (1 commit)

https://chromium.googlesource.com/angle/angle.git/+log/eeec3b14cc8d..1d97a4d0363d

$ git log eeec3b14c..1d97a4d03 --date=short --no-merges --format='%ad %ae %s'
2018-04-18 lucferron Revert "Fix dEQP renderbuffer unspecified attachment test."

Created with:
  roll-dep src/third_party/angle
BUG= chromium:833809 


The AutoRoll server is located here: https://angle-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=jmadill@chromium.org

Change-Id: I799a03dabb7ffa079c42dc0bbd6e7a59239a7150
Reviewed-on: https://chromium-review.googlesource.com/1019380
Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#552010}
[modify] https://crrev.com/4abe7b0fa63ea44106468ac4e0a5d67c3dd33c22/DEPS

The issue should now be fixed, avshaikh@, can you please verify and come back to me?

also, a screenshot of your chrome://gpu page would be really appreciated.

With response to C#10,
 
Retested this issue on Canary build #68.0.3404.0 on Win-10 touch device and the issue is fixed now. Kindly review an attached screen cast of latest canary behaviour and snapshot of chrome://gpu page.

Thank you..!!

Deleted: Input_pin.mp4 286 KB

	Input_pin.mp4 286 KB View Download

Deleted: chrome_gpu info.png 660 KB

	chrome_gpu info.png 660 KB View Download

avshaikh@etouch.net, is there any way to emulate touch events on a non-touch device, or do we need to purchase a touch device to reproduce this issue? From your about:gpu page you were running on ANGLE's D3D9 back-end, which may explain why other people were not able to reproduce the issue.

To use the D3D9 back-end deliberately the other testers can use --use-angle=d3d9 on the command line.

M67 Stable promotion is coming soon. Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and request a merge into the release branch ASAP. Thank you.

@Govind, the fix is already in. We're keeping this opened to investigate why we needed to revert our change because it was safe. We want to root cause it and find which component in chrome uses this feature potentially the wrong way and that fix, but it shouldn't be blocking the release.

Can in the chrome team help us reproduce the issue using the flag that Jamie pointed out above? (--use-angle=d3d9)

We might need to merge the fix to a release branch if the revert didn't reach them. We'll need to check if the revert made it into the chromium/3396 branch in ANGLE. Can you check Luc?

Ok I just verified and the revert did not make it to that branch.

OK, let's mark marge request. We should do a follow up issue for finding the culprit and re-landing the CL.

Fix is here:

https://chromium-review.googlesource.com/1017763

Should be very safe, and has baked in Canary and been verified externally. Affects Chrome back to M66, but we'll mark merge request in for 67 and 68. 

This bug requires manual review: DEPS changes referenced in bugdroid comments.
Please contact the milestone owner if you have questions.
Owners: cmasso@(Android), cmasso@(iOS), kbleicher@(ChromeOS), govind@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Approving merge to M67 branch 3396 for CL: https://chromium-review.googlesource.com/1017763 per comment #19. Pls merge ASAP. Thank you.

M68 is not branched yet so removing "Merge-Request-68" label.

The following revision refers to this bug:
  https://chromium.googlesource.com/angle/angle/+/5fd17eb7b7ba2d0b45b1ab12244d8db8ffbcee80

commit 5fd17eb7b7ba2d0b45b1ab12244d8db8ffbcee80
Author: Luc Ferron <lucferron@chromium.org>
Date: Wed Apr 25 18:25:19 2018

Revert "Fix dEQP renderbuffer unspecified attachment test."

This seems to have caused a regression in Chrome. I'm reverting the
change and suppressing the test that is failing on our end because of
it. Once we can confirm this solves the problem, we'll need some help
investigating further.

This reverts commit c0db9addeaebc76c7cc99b26aa27df5e432097ac.

Bug: angleproject:2321
Bug:  chromium:833809 
Change-Id: I5e40364217e15ae6117f5288a4754b25d983ca0a
Reviewed-on: https://chromium-review.googlesource.com/1017763
Commit-Queue: Luc Ferron <lucferron@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
(cherry picked from commit 1d97a4d0363da16a8d3ed942c515c0f738ed74e8)
Reviewed-on: https://chromium-review.googlesource.com/1028490
Reviewed-by: Geoff Lang <geofflang@chromium.org>

[modify] https://crrev.com/5fd17eb7b7ba2d0b45b1ab12244d8db8ffbcee80/src/tests/deqp_support/deqp_gles3_test_expectations.txt
[modify] https://crrev.com/5fd17eb7b7ba2d0b45b1ab12244d8db8ffbcee80/src/libANGLE/FramebufferAttachment.cpp

Is CL listed at #9 need merge to M67?

govind: The CL was merged to the chromium/3396 branch of ANGLE in comment #23, and should be picked up automatically on the next build for M67. I think we're good.

Great, thank you  jmadill@ for confirmation.