To add to this, opening multiple tabs seems to make the problem appear more often.  When closing a tab, the tab behind it is usually unresponsive.  If I close Chrome and re-open the tab history, the content area is functional again, but it will eventually cease functioning.  Can't open link, manipulate content, etc..

We have upgraded and downgraded SMART drivers and software to see if that helps, but it has no effect.  We see the same behavior with 16, 17, and 18.  Firefox functions normally to touch in all scenarios tested.

Tested the issue on chrome reported version 68.0.3440.106 using Windows-10 surfacepro and HP Elitebook with steps mentioned below:
1) Launched chrome reported version and navigated to some website
2) Able to scroll the page, navigated to the links, able to play the videos using touch.

As per comment# 0 from the reporter, as the issue seems to be related to SMARTBoards, hence routing this issue to MTV team to test and confirm the issue if SMARTBoards are available, hence adding TE-NeedsTriageFromMTV label to it and tentatively adding Internals>Input>Touch>Screen component to it.

Thanks!

Update from input team. Waiting for a triage from the QA team.

 Issue 875257  has been merged into this issue.

QA IND team don't have smartboard to test this issue and confirm the regression.

Could anyone from the MTV team have a look into this and check whether smartboard can be arranged and this issue can be tested @MTV. 

Thanks!

Unfortunately QA do not have smartboard for further triaging. Multiple bugs are being observed with respect to interaction of chrome with smart board. Seems like more relevant to Enterprise users.

farmers@ will it be possible for you to provide a bisect which helps us in identifying the bad commit which triggered this problem.

https://www.chromium.org/developers/bisect-builds-py

If possible we should consider a fix for M69.

I have never done a bisect as I'm not a developer, but I am willing to do whatever I can to with the issue.  SMART has released an updated driver to help with the issue, as well.  If it's necessary to point users to that driver, I will supply the link, but I assume, it should still be fixable in Chrome, as well.

https://support.smarttech.com/downloads/product-drivers/12_10-and-ink-5_3

M69 Stable promotion is coming VERY soon. Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and request a merge into the release branch ASAP. Merge has to happen latest by 4:00 PM PT Friday (08/24/18) in order to make it to next week stable cut. Thank you.

farmers@: If possible, a bisect would greatly help in this case. There's instructions here: https://www.chromium.org/developers/bisect-builds-py. It requires using the command line a bit but the commands are all on that page.

-RBS since we're unlikely to get a fix in for M69. I'm seeing if I can track down a SMARTboard locally.

farmers@: Do you know what model of the smart board you have?

bokan@: My issue was merged into this one as I'm having the exact same thing happen here at the district. I can tell you the Smartboard model we have if that will help. We have a few other models here, but this is the one we primarily use.

Smartboad SB680

aknowles@: thanks, does the issue occur on all smartboards or just that one?

bokan@: So far it's been happening on that model Smartboard when I've put in a Windows 10 Machine. We don't have many of the other models SB's and I don't think we've replaced any of those machines. We've been replacing them as they break down.

Ok thanks, we're trying to trackdown smartboard locally to see if we can reproduce the issue. In the mean time, if you're able to, a trace as described in comment #11 might be helpful if you're able to get one.

I'll see what I can do. Luckily, I'm doing maintenance on the computers today so I'll try to use it on one of them.

Updating label.

Removing Enterprise label per Enterprise triage as it's likely not an Enterprise bug.

bokan@: I was unable to do the bisect on Friday. Aside from running out of time, I had a hard time understanding the instructions to the bisect. I apologize for my ignorance.

aknowles@: Ok, thank you for trying. (The instructions are mainly meant for Chrome devs and QA team so they're a bit unfriendly for outsiders).

We'll wait until we can get a device locally.

This issue is persisting at my district as well. We've tried it on 17.1 with 68 stable and 16.0 with 68 and 69 stable. Issue persists. We need a resolution to this ASAP. We've got over 100 PCs with SMART Board 680s on Windows 10 with Chrome 69 stable installed and we CANNOT have this issue going widespread.

Wanted to comment that we are also seeing this issue. Same situation as others have reported. Hoped to have it resolve with the release of Chrome v69, but the issue persists. We are a GAFE District, so this issue is impacting all ~500 Teacher workstations that have SmartBoards connected.

Currently having our users switch to Edge for interactivity as a workaround.

We installed the updated SMART product drivers on a few today and are hoping this resolves it. I will report back once I hear from my teachers.

The NextAction date has arrived: 2018-09-13

>We installed the updated SMART product drivers on a few today and are hoping this resolves it. I will report back once I hear from my teachers.
Friendly ping, any results from the driver update?

We are still waiting for a device to check the issue locally.

Installing the updated SMART product drivers resolved it. Also, there's a windows update that resolves it as well. The KB is KB4346783. Enjoy :)

I'll keep this assigned to myself and will test again when we get our SMART board setup. If it was fine with our setup as well I'll close the bug.

Wanted to post up to confirm that the Windows Update fixes this issue.

It should be noted that the original update mentioned, KB4346783, has been superseded. The newest update containing this fix is KB4457128.

We've verified that the new SMART drivers DO NOT need to be installed for touch functionality to return to Chrome. Just the Windows update.

I have updated Windows to the most recent version and still no success. I have also updated Smart and it has still been unsuccessful.

@33. You've gotta be missing something. It's working on all of our PCs that we installed the kb and/or the SMART Product drivers update on. It works on both version 16 and 17 (updates inclusive).

@34

Perhaps you can give me the suggestion, this is what I have been doing.

Updating Windows with our Software Center.
Updating Windows via Windows Update to the most recent version.
Updating Smart Drivers to the most recent version.
Updating Smart Software to the most recent version.

Even our newly re-imaged units are experiencing this issue. All of them Windows 10. I've gone through settings, looked through this thread, etc.

Did you add the KBs to Software Center (had to ask. Sometimes people forget)? Also, what models are your SMART Boards just in case? You're on the right track so far.

We have Windows Update turned on as well, and it's been getting all of the updates.

As for the Smartboard Model SB680.

Let me keep this assigned to Lan as she is working on SMART board related issues.

@37. Hmm, OK. Are you on the latest version of Chrome? We have a couple of outliers here still that I'll be taking care of in the next week or so. Not sure if it just didn't get the update or not so I can't confirm the cause (WSUS on SCCM2012 has been working poorly as of late).

@39  We keep our systems as up to date as possible, and that includes Chrome.

Some computers where the Chrome was still working I updated to the latest version...only for the issue to crop up. It is quite the conundrum.

Has there been any progress on this issue? We're still experiencing it on all of our Smartboards with Windows 10. We have auto-update turned on for Chrome so it is keeping up to date. Same with SMART and Windows related updates.

We are looking into this as part of another issue.

@42, looking at the other issue you merged this with, I'm not seeing the correlation between the two.

@41, I have successfully eliminated the issue in my district by updating the SMART Product drivers to the latest and by installing the Windows KB that addresses this issue which I posted previously in this thread. My district is on Windows 10 1803 and we're using the SB600s.

Note: I believe you need to download the KB separately as it doesn't seem to install with normal Windows updates.