Display extension options in a WebUI overlay instead of in a new tab

chrome/renderer/resources/extensions/extension_options.js

Index: chrome/renderer/resources/extensions/extension_options.js
diff --git a/chrome/renderer/resources/extensions/extension_options.js b/chrome/renderer/resources/extensions/extension_options.js
index 854b550e19a1040efe2408a71a5bef43eec361a7..d88c3d1460a5bd490e6ba0ba423f1c3f03bf0863 100644
--- a/chrome/renderer/resources/extensions/extension_options.js
+++ b/chrome/renderer/resources/extensions/extension_options.js
@@ -13,10 +13,10 @@ var utils = require('utils');
 // Mapping of the autosize attribute names to default values
 var AUTO_SIZE_ATTRIBUTES = {
   'autosize': 'on',
-  'maxheight': 600,
-  'maxwidth': 800,
+  'maxheight': window.innerHeight,
+  'maxwidth': window.innerWidth,

[Dan Beam, 2014/08/14 19:01:27]

doesn't this only measure the size of the web contents rather than the whole
screen?  what coordinate system is AUTO_SIZE_ATTRIBUTES in?

[ericzeng, 2014/08/14 22:34:13]

By web contents do you mean the embedded web contents in the webview? I think
this should get the whole screen, since this custom element script is injected
into the embedder page (chrome://extensions-frame). 

   'minheight': 32,
-  'minwidth': 80
+  'minwidth': 32
 };
 
 function ExtensionOptionsInternal(extensionoptionsNode) {