Limit scope of settings API configuration and proxy permission

chrome/common/extensions/api/types.json

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 [
   {
     "namespace": "types",
     "description": "The <code>chrome.types</code> API contains type declarations for Chrome.",
     "types": [
       {
@@ skipping 28 matching lines @@
                   {
                     "name": "details",
                     "type": "object",
                     "description": "Details of the currently effective value.",
                     "properties": {
                       "value": {
                         "description": "The value of the setting.",
                         "type": "any"
                       },
                       "levelOfControl": {
-                        "description": "One of<ul><li><var>not_controllable</var>: cannot be controlled by any extension</li><li><var>controlled_by_other_extensions</var>: controlled by extensions with higher precedence</li><li><var>controllable_by_this_extension</var>: can be controlled by this extension</li><li><var>controlled_by_this_extension</var>: controlled by this extension</li></ul>",
+                        "description": "One of<ul><li><var>not_controllable</var>: cannot be controlled by this extension due to lack of permission or cannot be controlled by any extension</li><li><var>controlled_by_other_extensions</var>: controlled by extensions with higher precedence</li><li><var>controllable_by_this_extension</var>: can be controlled by this extension</li><li><var>controlled_by_this_extension</var>: controlled by this extension</li></ul>",

[Bernhard Bauer, 2014/03/04 17:31:18]

Hm... if an extension doesn't have incognito permissions, should we even allow
reading the proxy settings for incognito? And in that case, it shouldn't happen
that we will tell the extension that it can't change the value because it
doesn't have incognito permissions.

[battre, 2014/03/05 08:34:36]

Yes, you are right. In case the extension does not have incognito permission, we
don't allow reading the value. I have reverted the string. Good catch.

Done.

                         "type": "string",
                         "enum": ["not_controllable", "controlled_by_other_extensions", "controllable_by_this_extension", "controlled_by_this_extension"]
                       },
                       "incognitoSpecific": {
                         "description": "Whether the effective value is specific to the incognito session.<br/>This property will <em>only</em> be present if the <var>incognito</var> property in the <var>details</var> parameter of <code>get()</code> was true.",
                         "type": "boolean",
                         "optional": true
                       }
                     }
                   }
@@ skipping 107 matching lines @@
             "optional": true,
             "minimum": 0,
             "maximum": 100,
             "description": "When format is <code>\"jpeg\"</code>, controls the quality of the resulting image.  This value is ignored for PNG images.  As quality is decreased, the resulting image will have more visual artifacts, and the number of bytes needed to store it will decrease."
           }
         }
       }
     ]
   }
 ]