Closed GoogleCodeExporter closed 9 years ago
Issue chromium:103033 has been merged into this issue.
Original comment by kkania@chromium.org
on 6 Mar 2012 at 1:03
After some discussion (http://codereview.chromium.org/9617025/), I've decided
not to take action on this issue. Allowing disabling enterprise-enforced
extensions in chromium circumvents the purpose of enterprise policy. However,
it might be ok to, after Chrome starts up, disable any running external
extensions and try to restore a clean environment (e.g., maybe close a tab the
extension opened).
I do not think this is worthwhile currently. Outside of ChromeDriver itself,
the options available to the user to get around these issues are to:
1) get admin privileges and disable the policy
2) use an existing profile (this helps if the extension does something only for
new profiles)
Original comment by kkania@chromium.org
on 17 Apr 2012 at 4:48
Not all external extensions are enterprise-enforced.
LastPass, for instance, installs itself as an external extension by default,
and opens a new tab everytime you load a new profile.
This is a serious PITA if you're trying to run tests, but I'd rather not have
to abandon my password manager.
Original comment by daniel.r.heath
on 13 Nov 2012 at 4:14
Original comment by kkania@chromium.org
on 13 Mar 2013 at 11:45
Original comment by kkania@chromium.org
on 14 Mar 2013 at 9:14
Original comment by samu...@chromium.org
on 21 Feb 2015 at 12:27
Original issue reported on code.google.com by
kkania@chromium.org
on 30 Jan 2012 at 5:31