Re:Show HN: Screen.rip – API for capturing web screenshots
by mpetrovich on Thursday October 19, 2017 @08:47AM
(#15507389)
If it’s using Chrome headless, it’s superior to wkhtmltopdf. The latter has lots of little gotchas and things that may render fine in a browser but not in wkhtmltopdf. Chrome headless doesn’t suffer from those issues, obviously.
Re:Show HN: Screen.rip – API for capturing web screenshots
by gotrecruit on Thursday October 19, 2017 @09:13AM
(#15507558)
but the site itself says it "runs headless".
Re:Show HN: Screen.rip – API for capturing web screenshots
by htgb on Thursday October 19, 2017 @09:30AM
(#15507668)
Running headless does not imply that it's running Chrome headless, just that it runs without a GUI.
Re:Show HN: Screen.rip – API for capturing web screenshots
by have_faith on Thursday October 19, 2017 @08:26AM
(#15507267)
One is a hosted service and one isn't.
Re:Show HN: Screen.rip – API for capturing web screenshots
by lucapinello on Thursday October 19, 2017 @09:06AM
(#15507498)
I know but if I need to use an API to an external server I can also launch a command locally. 7$ is not much but I don't see any real benefit unless you want to capture a subsection of a website.
Re:Show HN: Screen.rip – API for capturing web screenshots
by tyingq on Thursday October 19, 2017 @08:33AM
(#15507304)
The clip to a specific DOM element seems unique to this.
Re:Show HN: Screen.rip – API for capturing web screenshots
by laktek on Thursday October 19, 2017 @08:54AM
(#15507437)
Also with screen.rip, you can run a custom JS before capturing the screenshot and also can wait for certain elements to appear (which is quite important today with client-side rendered sites)
Disclaimer: I created screen.rip
https://wkhtmltopdf.org/