A lot of the existing Content Settings on Chrome OS are missing from MD Settings. I captured what's in the existing Settings vs MD Settings here: https://docs.google.com/spreadsheets/d/1bVRBeEcJ3YSJNMKq9U9pm-dGFtVRDryzfojoDeYpirI/edit#gid=0
I can also audit Content Settings on Desktop if that would be useful.
This will block MD Settings from launching to Dev Channel, so marking as a P1.
For posterity - doc by emilyschecter@ on changes reviewed by Security/Privacy
https://docs.google.com/spreadsheets/d/1Bil59vAuGTMN53S5j8J5BVAVit0NWSGekMYOZFqCR3w/edit#gid=0
CHANGES
- Camera/Mic: chooser drop down
- Cookies: clear on exit checkbox; Flash Player settings link; clear on exit by site; all cookies and site data management
- Handlers: Handlers with associated sites and ability to set which one is the default/delete it
- Zoom: list with delete options
- USB: device and its related sites, also shown in the single site settings page
- General learn more: blue link appended to site lists
- General exceptions: added site exception link in allow state and modified dialog text (to be handled in this bug: https://bugs.chromium.org/p/chromium/issues/detail?id=442446)
- Incognito support: checkbox in the exception dialog that shows when you've got an incognito window open
NO MOCKS
- Unsandboxed plugin access (ask/block)
- Automatic downloads (ask/block)
- Images (allow/block)
- Plugins (allow important/block - approved by Privacy in Emily's doc)
- Location (ask/block)
- Notifications (ask/block)
- JavaScript (allow/block)
- Pop-ups (allow/block)
- Autoplay (allow/block) [note this is going through UI Review so may change]
- Keygen (allow/block)
- Background sync (allow/block)
- Midi (allow/block)
STRINGS (For desktop-only allow/block options)
- MIDI: Ask before allowing sites to use your MIDI (recommended)
- Handlers: Ask before allowing sites to be become default handlers (recommended)
- Unsandboxed plugin access: Ask first before allowing unsandboxed plugin content to run (recommended)
- Images: Allow sites to show images (recommended)
- Plugins: Allow important plugin content to run (recommended)
This bug was getting a bit unwieldy and hard to figure out what was remaining. Since dschuyler is pitching in on Site Settings I decided to review the mocks, try to figure out what I think is remaining and split it into separate bugs. I'm hanging each bug off of this bug, for tracking purposes. When all bugs have been resolved, we can close this one.
That was supposed to read: Since dschuyler is pitching in on Site Settings Dave and I decided it would be helpful if I reviewed the mocks, try to figure out what I think is remaining [...]
Comment 1 by tbuck...@chromium.org
, May 25 2016