(browserflow.app)

707 points namukang | 1 comments | 17 Nov 21 15:16 UTC | HN request time: 0.263s | source

Show context

tyingq ◴[17 Nov 21 18:09 UTC] No.29256582[source]▶

Too bad headless chrome seems uninterested in supporting browser extensions..."wontfix"

Otherwise, you could make a pretty neat self-hosted "cloud" of this nice looking scraper extension.

hoten ◴[18 Nov 21 01:55 UTC] No.29261213[source]▶

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

replies(1): >>29261540 #

tyingq ◴[18 Nov 21 02:59 UTC] No.29261540[source]▶

Sounds promising, thanks for sharing! "--headless=chrome" isn't google searchable, so I'm still looking for details.

replies(1): >>29275210 #

neop1x ◴[19 Nov 21 09:04 UTC] No.29275210[source]▶

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-c...

replies(1): >>29284822 #

tyingq ◴[20 Nov 21 01:41 UTC] No.29284822[source]▶

Oh, then it isn't helpful news. Headless does not support extensions.

replies(1): >>29367757 #

1. hoten ◴[28 Nov 21 10:21 UTC] No.29367757[source]▶

I mean the CLI flag. I suppose it's called a switch. And yes, it does support extensions if you do --headless=chrome

Show HN: I made a Chrome extension that can automate any website