3 ms·

Too bad headless chrome seems uninterested in supporting browser extensions..."wontfix" https://bugs.chromium.org/p/chromium/issues/detail?id=706008 https://bu

by tyingq 5y ago

Too bad headless chrome seems uninterested in supporting browser extensions..."wontfix" https://bugs.chromium.org/p/chromium/issues/detail?id=706008 https://bugs.chromium.org/p/chromium/issues/detail?id=706008 Otherwise, you could make a pretty neat self-hosted "cloud" of this nice looking scraper extension.

hoten 5y ago
Recently a `--headless=chrome` flag was added to run headless mode using actual chrome browser code, which means extensions are now supported!
- tyingq 5y ago
  Sounds promising, thanks for sharing! "--headless=chrome" isn't google searchable, so I'm still looking for details.
  - neop1x 5y ago
    Isn't the "chrome" value for "headless" parameter ignored? Maybe he simply meant the --headless switch (since Chrome 59) https://developers.google.com/web/updates/2017/04/headless-chrome https://developers.google.com/web/updates/2017/04/headless-c... EDIT: --headless is under kHeadless https://sourcegraph.com/search?q=context:global+repo:chromium/chromium+kHeadless&patternType=literal https://sourcegraph.com/search?q=context:global+repo:chromiu...
    - tyingq 5y ago
      Oh, then it isn't helpful news. Headless does not support extensions.
      - hoten 5y ago
        I mean the CLI flag. I suppose it's called a switch. And yes, it does support extensions if you do --headless=chrome
namuorg 5y ago
I built Browserflow Cloud for that purpose ;) It was a lot of work translating the extension code to work with headless browsers, but it means you can deploy your flows to the cloud and have it run automatically!
- tyingq 5y ago
  Yes, sure. Just that some use cases, like internal applications that aren't exposed to the internet, or dev instances of those that are, would be difficult.
  - mritchie712 5y ago
    What type of app did you have in mind?
    - fragmede 5y ago
      automation/screenshotting of a bespoke internal ticketing system (aka not-Jira), but without needing to have my laptop on.

by tyingq 5y ago

hoten 5y ago

Recently a `--headless=chrome` flag was added to run headless mode using actual chrome browser code, which means extensions are now supported!

tyingq 5y ago
Sounds promising, thanks for sharing! "--headless=chrome" isn't google searchable, so I'm still looking for details.
- neop1x 5y ago
  Isn't the "chrome" value for "headless" parameter ignored? Maybe he simply meant the --headless switch (since Chrome 59) https://developers.google.com/web/updates/2017/04/headless-chrome https://developers.google.com/web/updates/2017/04/headless-c... EDIT: --headless is under kHeadless https://sourcegraph.com/search?q=context:global+repo:chromium/chromium+kHeadless&patternType=literal https://sourcegraph.com/search?q=context:global+repo:chromiu...
  - tyingq 5y ago
    Oh, then it isn't helpful news. Headless does not support extensions.
    - hoten 5y ago
      I mean the CLI flag. I suppose it's called a switch. And yes, it does support extensions if you do --headless=chrome

namuorg 5y ago

I built Browserflow Cloud for that purpose ;) It was a lot of work translating the extension code to work with headless browsers, but it means you can deploy your flows to the cloud and have it run automatically!

tyingq 5y ago
Yes, sure. Just that some use cases, like internal applications that aren't exposed to the internet, or dev instances of those that are, would be difficult.
- mritchie712 5y ago
  What type of app did you have in mind?
  - fragmede 5y ago
    automation/screenshotting of a bespoke internal ticketing system (aka not-Jira), but without needing to have my laptop on.