2

When I install an extension in Google Chrome using Group Policy ExtensionInstallForcelist (http://dev.chromium.org/administrators/policy-list-3#ExtensionInstallForcelist), the extension is indeed installed & prevents removal or disabling - however, the following options are no longer available/visible on the Chrome Extensions page for this extension:

Allow in incognito

Allow access to file URLs

Options

If possible, I'd like to also force (or default) "Allow in incognito" to be enabled, but if that's not possible, I at least need to give the user the ability to enable this option. Is there anything I can do about this? I believe I've read all the related documentation, and I haven't found anything...

Thank you for any help you can provide!

Community
  • 1
  • 1
schwtyl
  • 21
  • 1
  • 4

1 Answers1

1

This was already answered here: Can I run extension in incognito mode by default?.

I believe it was already requested as a feature request, how about starring or commenting there?

Edit: Apparently there is also an open bug over here

Community
  • 1
  • 1
tutuDajuju
  • 10,307
  • 6
  • 65
  • 88
  • That may answer part of the question, though the root question still stands: why does ExtensionInstallForcelist remove the “Allow in incognito” option altogether, and is there anything I can do about it? Yes, I would like to auto-default it to checked, but I'd also settle for the user being able to check the box - but the box is hidden altogether. This behavior is not documented anywhere (that I've seen), hence my question here. I've seen nowhere that discusses "Allow in Incognito" in relation to these Group Policies. – schwtyl Nov 12 '12 at 17:15
  • Hmm, is IncognitoModeAvailability policy set to 1 by any chance? or IncognitoEnabled to disabled? – tutuDajuju Nov 12 '12 at 18:26
  • Nope, Incognito mode is enabled, and IncognitoModeAvailability is unset. When I use Incognito, my extension is not active - but it is active in Incognito when "Allow in Incognito" is checked on the Extensions page (when the extension is installed normally). I'm also not sure if I should consider this a "bug", or a "feature"... I've also verified that this behavior is identical on Windows and Mac for ExtensionInstallForcelist, with the latest stable Chrome. – schwtyl Nov 12 '12 at 18:46
  • This should probably files as a bug since at the very least it's an undocumented behavior... – tutuDajuju Nov 13 '12 at 11:53
  • 1
    FYI to anyone interested, there is an open Chromium issue regarding this: [link](https://code.google.com/p/chromium/issues/detail?id=224857) – schwtyl Jun 12 '13 at 19:17