Version of Google Chrome (Wrench-> About Google Chrome): 66.0.3359.139 (Official Build) (64-bit)
Version of MSI (if applicable): Not Applicable, from auto-update
Using group policy settings? No

We use a 'screen scraper' program called Laserfiche Connector to read text or do OCR of a window to get the contents of a page from a web enabled application. The documentation and information about Connector is here:

https://www.laserfiche.com/support/webhelp/Laserfiche/10/en-us/administration/#../Subsystems/Connector/Content/About.htm

There's a test utility with Connector that, when an icon is dragged onto an application window, should return information about the application. After the most recent update to Chrome, it is no longer able to see Chrome. I've attached a zip file containing the x64 test utility.

I tried opting out of the Site Isolation program, but that did not fix the issue.

This problem occurs with a few different versions of Laserfiche Connector. Laserfiche's advice on how to configure Chrome to work with Connector are as follows:

Chrome
If you are running Laserfiche Connector from Chrome, you need to either configure a remote debugger for Chrome or render accessibility parameters, depending on if you selected Use JavaScript to detect controls or Use UI automation to detect controls in the profile wizard.

If you are using JavaScript

Confirm that the LFC.exe.config file (located in the Laserfiche Connector installation directory) has the following entry to allow remote debugging in Chrome.
<setting name="ChromeRemoteServer" serializeAs="String">

<value>http://localhost:portnumber</value>

</setting>

Copy the port number. (It will be used in step 4.) If you choose to change port, the port number must be between 1 and 65535, and it is best not to use the common port.
Open Google Chrome's properties by right-clicking Google Chrome in the Start menu and selecting Properties. (If you are using Windows 10, right-click Google Chrome in the Start menu, point to More, select Open file location, and then right-click the shortcut there.) If Chrome.exe is not in the Start menu, you can drag it there and then open its properties.
In the Shortcut tab, add --remote-debugging-port=portnumber to the end of the contents in the Target text box. (Ensure there is a space between the target and the parameter.) The port number must be the same as the port number in the LFC.exe.config file above.
Click Apply.
Restart both Chrome and Laserfiche Connector. If Chrome is pinned to your taskbar, un-pin and then re-pin it.
If you are using UIAutomation instead of JavaScript

Configure the --force-renderer-accessibility parameter to run when chrome.exe starts. You can do this by adding the parameter to the target property of for each Chrome start shortcut.

Open Google Chrome's properties by right-clicking Google Chrome in the Start menu and selecting Properties. If Chrome.exe is not in Start menu, drag it into Start menu and then open its properties.
Configure the --force-renderer-accessibility parameter to run when chrome.exe starts. You can do this by adding the parameter to the target property of for each Chrome start shortcut.
In the Shortcut tab, add --force-renderer-accessibility to the end of the contents in the Target text box. (Ensure there is a space between the target and the parameter.)
Click Apply and restart the application. If Chrome is pinned to your taskbar, un-pin and then re-pin it.

 

Deleted: ConnectorTestUtilityx64.zip 2.8 MB

ConnectorTestUtilityx64.zip 2.8 MB Download