Chrome Extensions

[de...@atlascode.com]

Will the headless chrome allow chrome extensions to be installed?

I would like to use headless chrome to fire up a web page and have a chrome extension run on that page which modifies the DOM. Then take a screenshot of the result.

Thanks for putting in the work to make chrome headless, I think it will allow for a lot of cool interesting projects.

[Alex Clarke]

Sorry we don't have any plans to support chrome extensions in headless.  The reason being extensions are a part of the chrome/ layer which doesn't exist in headless.  You can however execute JS on a target page using DevTool's Runtime.evaluate.  Does that do what you want or was the extension itself something you wanted to test?

E.g. https://cs.chromium.org/chromium/src/headless/app/headless_shell.cc?q=evaluate+f:headless/&sq=package:chromium&l=106&dr=C

--
You received this message because you are subscribed to the Google Groups "headless-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev...@chromium.org.
To post to this group, send email to headle...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/1df78234-49c3-4166-93de-14e3ef8b7b83%40chromium.org.

[de...@atlascode.com]

Unfortunately it was the combination of the extension and the page that I wanted to test. But I appreciate your prompt response.

[ak...@zipsocket.com]

We also were hoping to use the headless chrome (puppeteer) to test our application. It is a screen-sharing application, so much of the functionality on chrome is gated behind an extension. Still no plans to support extensions in headless?

[Alex Clarke]

On 30 October 2017 at 23:32, <ak...@zipsocket.com> wrote:

We also were hoping to use the headless chrome (puppeteer) to test our application. It is a screen-sharing application, so much of the functionality on chrome is gated behind an extension. Still no plans to support extensions in headless?

Sorry no, and I don't foresee this changing because supporting extensions is a lot of work.

 

On Thursday, June 9, 2016 at 8:18:36 AM UTC-7, de...@atlascode.com wrote:

Unfortunately it was the combination of the extension and the page that I wanted to test. But I appreciate your prompt response.

On Thursday, June 9, 2016 at 4:16:39 PM UTC+1, Alex Clarke wrote:

Sorry we don't have any plans to support chrome extensions in headless.  The reason being extensions are a part of the chrome/ layer which doesn't exist in headless.  You can however execute JS on a target page using DevTool's Runtime.evaluate.  Does that do what you want or was the extension itself something you wanted to test?

E.g. https://cs.chromium.org/chromium/src/headless/app/headless_shell.cc?q=evaluate+f:headless/&sq=package:chromium&l=106&dr=C

On Thu, Jun 9, 2016 at 4:04 PM, <de...@atlascode.com> wrote:

Will the headless chrome allow chrome extensions to be installed?

I would like to use headless chrome to fire up a web page and have a chrome extension run on that page which modifies the DOM. Then take a screenshot of the result.

Thanks for putting in the work to make chrome headless, I think it will allow for a lot of cool interesting projects.

--
You received this message because you are subscribed to the Google Groups "headless-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev...@chromium.org.
To post to this group, send email to headle...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/1df78234-49c3-4166-93de-14e3ef8b7b83%40chromium.org.

--
You received this message because you are subscribed to the Google Groups "headless-dev" group.

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

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

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/3602c0c7-5232-43fd-b7cd-c8a191ffaf1e%40chromium.org.

[Justin Yeap]

Hi Alex, i think it would be helpful if this becomes possible as it widens the use cases this can have for many. I believe this creates alot of dealbreakers for many companies including the one i am working in now, we are considering switching back to Normal Chrome for testing due to this issue.

On Tuesday, October 31, 2017 at 4:23:49 PM UTC+8, Alex Clarke wrote:

On 30 October 2017 at 23:32, <ak...@zipsocket.com> wrote:

We also were hoping to use the headless chrome (puppeteer) to test our application. It is a screen-sharing application, so much of the functionality on chrome is gated behind an extension. Still no plans to support extensions in headless?

Sorry no, and I don't foresee this changing because supporting extensions is a lot of work.

 

On Thursday, June 9, 2016 at 8:18:36 AM UTC-7, de...@atlascode.com wrote:

Unfortunately it was the combination of the extension and the page that I wanted to test. But I appreciate your prompt response.

On Thursday, June 9, 2016 at 4:16:39 PM UTC+1, Alex Clarke wrote:

Sorry we don't have any plans to support chrome extensions in headless.  The reason being extensions are a part of the chrome/ layer which doesn't exist in headless.  You can however execute JS on a target page using DevTool's Runtime.evaluate.  Does that do what you want or was the extension itself something you wanted to test?

E.g. https://cs.chromium.org/chromium/src/headless/app/headless_shell.cc?q=evaluate+f:headless/&sq=package:chromium&l=106&dr=C

On Thu, Jun 9, 2016 at 4:04 PM, <de...@atlascode.com> wrote:

Will the headless chrome allow chrome extensions to be installed?

I would like to use headless chrome to fire up a web page and have a chrome extension run on that page which modifies the DOM. Then take a screenshot of the result.

Thanks for putting in the work to make chrome headless, I think it will allow for a lot of cool interesting projects.

--
You received this message because you are subscribed to the Google Groups "headless-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev...@chromium.org.
To post to this group, send email to headle...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/1df78234-49c3-4166-93de-14e3ef8b7b83%40chromium.org.

--
You received this message because you are subscribed to the Google Groups "headless-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev...@chromium.org.
To post to this group, send email to headle...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/3602c0c7-5232-43fd-b7cd-c8a191ffaf1e%40chromium.org.

[Eric Seckler]

See https://crbug.com/706008 and the linked doc for the rationale of why we're not currently planning on adding extension support.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/f536975d-fa0f-4522-a1ca-5b128c244cbb%40chromium.org.

[de...@atlascode.com]

We did actually go back to using full chrome for our testing system for this reason.

[Justin Yeap]

@de...@atlascode.com, do you mind sharing how did u do the chrome controlling, we are attempting x server.

[de...@atlascode.com]

We wrote a chrome extension that would load a set of test run steps from a json file, it would then send events to the page for keyboard and mouse input to simulate a user. As it was a chrome extension, we could then just install it in our regular instances of chrome and watch the tests being executed and know that the tests would be executed the exact same way on the server because it was also using full chrome with the same extension. The extension also has the ability to record tests and save the test steps to a json file so it keeps everything together.

[Justin Yeap]

Thanks for sharing, seems a bit of manual work required. Did u guys consider xvfb ?

[de...@atlascode.com]

It was a lot of work. We were running in a windows server environment so didn't consider xvfb.

[Justin Yeap]

I see, Thanks for the reply, did you all consider selenium instead ?