Whitelist Topaz extension for Public Sessions
Reported by
mhans...@good-sam.com,
Sep 28 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36 Platform: 9460.73.1 (Official Build) stable-channel auron_yuna Steps to reproduce the problem: 1. Connect Topaz signature pad 2. Attempt to capture signature in Chrome What is the expected behavior? What went wrong? I'd like to add this extension to a machine in Public Session mode to allow users to capture signatures with a Topaz signature pad. WebStore page: https://chrome.google.com/webstore/detail/topaz-sigplusextlite-back/dhcpobccjkdnmibckgpejmbpmpembgco?hl=en-US Did this work before? N/A Chrome version: 59.0.3071.134 Channel: stable OS Version: 9460.73.1 Flash Version: 26.0.0.102
,
Oct 11 2017
Please review sduraisamy@
,
Oct 11 2017
Adding debugs logs where we force in stall the topaz extension for a device on Chrome 60.0.3112.80
,
Oct 25 2017
Additional research has revealed that this extension does not provide full functionality for the Topaz signature pad in ChromeOS. There is also an .ocx file that is required which is incompatible with *nix. It appears this extension was only built for Chrome browser on Windows systems.
,
Oct 26
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||
►
Sign in to add a comment |
|||
Comment 1 by alu...@chromium.org
, Sep 28 2017Labels: Hotlist-Enterprise