Audit content settings on Chrome OS |
|||||
Issue descriptionFrom issue 688485 : We should investigate hiding sections on Chrome OS entirely that may not apply: * PDF documents * Unsandboxed plugin access * MIDI * USB Devices The following have not been tested on Chrome OS in guest mode (testing is complicated or not obvious): * Background sync * Automatic downloads * Handlers
,
Feb 16 2017
,
Feb 20 2017
,
Apr 17 2017
* Verified background sync toggle works in non-guest and guest mode. * Automatic downloads - I'm still not sure how to test this, but can not imagine there is anything special about this on Chrome OS. * Handlers - these have been disabled in guest mode. Leaving this open as we should probably document the validity of the issues mentioned, but removing the milestone marker.
,
Apr 18 2017
With ARC++ apps able to open to PDFs, I could see keeping the PDF content settings around. I believe there are also MIDI/USB APIs that work on Chrome OS, no?
,
Apr 18 2017
The PDF setting is "Open PDFs using a different application". On Chrome OS, if that is enabled, PDF files are downloaded instead of opened in the browser, which is a little odd / unexpected. As for MIDI/USB APIs on Chrome OS - I have no idea, thus this bug :)
,
Apr 18 2017
Re #6 PDF, see some discussion in here: 700118
,
Apr 18 2017
,
Apr 18 2017
Sounds like PDF behavior is confusing in the same way on all platforms, so that just leaves the following to investigate on CrOS: * Unsandboxed plugin access * MIDI * USB Devices
,
Apr 21 2017
It looks like there are web APIs for both MIDI and USB, and I'd assume they are available on Chrome OS: USB: https://developers.google.com/web/updates/2016/03/access-usb-devices-on-the-web MIDI: https://www.keithmcmillen.com/blog/making-music-in-the-browser-web-midi-api/ Not sure we support unsandboxed plugins though
,
Apr 13 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by steve...@chromium.org
, Feb 13 2017