Issue metadata
Sign in to add a comment
|
now that apps will be gone extensions need access to serial port
Reported by
s.buer...@gmail.com,
May 27 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce the problem: 1. create extension with `serial` as a permission requirement in the manifest.json file 2. load unpacked extension 3. see error What is the expected behavior? I expect that an extension has access to serial ports now that apps are sunsetting. This is the suggested route for migration and there are no other options (serial port doesnt live on the web). What went wrong? When attempting to load my unpacked extension I get the following error message: `'serial' is only allowed for packaged apps, but this is a extension.` Did this work before? N/A Chrome version: 58.0.3029.110 Channel: stable OS Version: OS X 10.11.6 Flash Version: See my stackoverflow issue which redirected me here: https://stackoverflow.com/questions/44217146/chrome-extension-how-to-use-serial-port-now-that-apps-are-sunsetting
,
May 31 2017
Could you please provide us any sample extension to reproduce the error from test team end. Thanks,
,
May 31 2017
Any empty extension that has `serial` in the manifest file will do.
,
May 31 2017
Thank you for providing more feedback. Adding requester "kavvaru@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 1 2017
We are not able to find out any such extension to test the issue from our end. Please provide a sample extension for further triaging. Thanks!!
,
Jun 7 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by pfeldman@chromium.org
, May 30 2017