Re: [crx] Auto enable external extension installation

1,083 views
Skip to first unread message

Jeffrey Yasskin

unread,
Mar 11, 2013, 2:29:37 PM3/11/13
to leslie...@gmail.com, Chromium-extensions
No, there's not. The user needs to explicitly tell chrome they want
your extension. There's a lot of malware that installs itself in the
same way, and we use this extra step to help distinguish.

Sorry for the inconvenience.

On Mon, Mar 4, 2013 at 9:58 PM, <leslie...@gmail.com> wrote:
> I am developing an automatic testing tool and we wanna test on Chrome. So we
> built a Chrome extension and install it as an external extension via
> preference file. But we find this extension is disabled by default in Chrome
> and user should enable it manually.
> So this blocks us and is there any way to do this enable work automatically?
> Is there such setting?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Chromium-extensions" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to chromium-extens...@chromium.org.
> To post to this group, send email to chromium-...@chromium.org.
> Visit this group at
> http://groups.google.com/a/chromium.org/group/chromium-extensions/?hl=en.
> For more options, visit
> https://groups.google.com/a/chromium.org/groups/opt_out.
>
>

er...@links.ee

unread,
Jul 10, 2013, 9:32:02 PM7/10/13
to chromium-...@chromium.org, leslie...@gmail.com
The user already has to confirm the addition through the 'Add to Chrome' popup dialog when the extension is downloaded! So why the additional step?!?

This simply creates *redundant* user friction for installation of extensions, it seems.

Best, -E.


On Monday, March 11, 2013 11:29:37 AM UTC-7, Jeffrey Yasskin wrote:
No, there's not. The user needs to explicitly tell chrome they want
your extension. There's a lot of malware that installs itself in the
same way, and we use this extra step to help distinguish.

Sorry for the inconvenience.

On Mon, Mar 4, 2013 at 9:58 PM,  <leslie...@gmail.com> wrote:
> I am developing an automatic testing tool and we wanna test on Chrome. So we
> built a Chrome extension and install it as an external extension via
> preference file. But we find this extension is disabled by default in Chrome
> and user should enable it manually.
> So this blocks us and is there any way to do this enable work automatically?
> Is there such setting?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Chromium-extensions" group.
> To unsubscribe from this group and stop receiving emails from it, send an

Finnur Thorarinsson

unread,
Jul 11, 2013, 6:35:29 AM7/11/13
to er...@links.ee, Chromium-extensions, leslie...@gmail.com
FWIW: Instead of *installing* the extension I believe you can still load an unpacked extension from a directory, if that helps you...

chrome.exe --load-extension=c:\path\extension_directory

(where extension_directory is the directory that contains your manifest.json and other extension files).


To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.

To post to this group, send email to chromium-...@chromium.org.

Eric Peterson

unread,
Jul 11, 2013, 3:00:40 PM7/11/13
to Finnur Thorarinsson, Chromium-extensions
Thanks for the suggestion, Finnur.

I'm simply trying to make the user's experience of downloading & installing an extension from the Chrome Web Store as frictionless and easy as possible. 

The user already has to confirm that they 'want to add the extension to Chrome' via the automatic popup dialog in the Chrome store --this insured that user was aware of the installation. Now it's *also* necessary to coach them through the configuration of extensions through Chrome's settings.

This makes for a very cumbersome adoption process for Chrome extensions. I understand the need for safety, but this is, imo, redundant and unnecessarily awkward. Fewer users will be willing to take the steps.

If you have a say in this part of the spec, kindly pass my concerns along. :)

Thanks again, -E.

-- 
Eric Peterson
Sent with Sparrow

Finnur Thorarinsson

unread,
Jul 11, 2013, 7:13:01 PM7/11/13
to Eric Peterson, Chromium-extensions
I'm confused. It is 11pm my time and I've had a long day, so maybe it is too late for me to be replying. However, this thread started as "the sideload warning is interrupting with my automated testing tool" but has suddenly morphed into "users have too many obstacles downloading something from the webstore". Can you connect the dots here for me as I'm not sure I understand how these two are related.

john simth

unread,
Jun 7, 2014, 8:29:14 PM6/7/14
to chromium-...@chromium.org, er...@links.ee, leslie...@gmail.com
Hi Finnur Thorarinsson ,

                                          Your Seems to Be Working Great Still we Can Load Extensions from a Local Directory....

On Thursday, July 11, 2013 4:05:29 PM UTC+5:30, Finnur Thorarinsson wrote:
FWIW: Instead of *installing* the extension I believe you can still load an unpacked extension from a directory, if that helps you...

chrome.exe --load-extension=c:\path\extension_directory

(where extension_directory is the directory that contains your manifest.json and other extension files).
On Thu, Jul 11, 2013 at 1:32 AM, <er...@links.ee> wrote:
The user already has to confirm the addition through the 'Add to Chrome' popup dialog when the extension is downloaded! So why the additional step?!?

This simply creates *redundant* user friction for installation of extensions, it seems.

Best, -E.


On Monday, March 11, 2013 11:29:37 AM UTC-7, Jeffrey Yasskin wrote:
No, there's not. The user needs to explicitly tell chrome they want
your extension. There's a lot of malware that installs itself in the
same way, and we use this extra step to help distinguish.

Sorry for the inconvenience.

On Mon, Mar 4, 2013 at 9:58 PM,  <leslie...@gmail.com> wrote:
> I am developing an automatic testing tool and we wanna test on Chrome. So we
> built a Chrome extension and install it as an external extension via
> preference file. But we find this extension is disabled by default in Chrome
> and user should enable it manually.
> So this blocks us and is there any way to do this enable work automatically?
> Is there such setting?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Chromium-extensions" group.
> To unsubscribe from this group and stop receiving emails from it, send an

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extensions+unsub...@chromium.org.
To post to this group, send email to chromium-...@chromium.org.
Reply all
Reply to author
Forward
0 new messages