gwuhaolin/chrome-render issues and pull requests

#19 - Project still alive? Latest updates for nodejs and Chrome?

Issue - State: open - Opened by ghost over 6 years ago

#18 - No Chrome environment, please install Chrome 59+!

Issue - State: open - Opened by GavinFreedom over 6 years ago - 3 comments

#17 - Clean example with await

Pull Request - State: closed - Opened by kirkov almost 7 years ago

#16 - Fix unhandled rejections in rare cases

Pull Request - State: closed - Opened by SkeLLLa about 7 years ago

#15 - Add option to control page blank

Pull Request - State: closed - Opened by SkeLLLa about 7 years ago - 2 comments

#14 - Feature/document event

Pull Request - State: closed - Opened by SkeLLLa about 7 years ago

#13 - Use document event instead of console.log in useReady

Issue - State: closed - Opened by SkeLLLa about 7 years ago - 6 comments

#12 - fix proper release of tab

Pull Request - State: closed - Opened by SkeLLLa about 7 years ago - 3 comments

#11 - Join efforts with usus?

Issue - State: closed - Opened by gajus about 7 years ago

#10 - How to get the whole page content (the part render by js)

Issue - State: closed - Opened by tracyshen about 7 years ago - 3 comments
Labels: question

#9 - Configure host/port

Issue - State: closed - Opened by ttonyh about 7 years ago - 1 comment

#8 - Started to get "Could not find node with given id"

Issue - State: closed - Opened by gajus about 7 years ago - 14 comments

#7 - cookies setting (it appears) causes chrome-remote-interface to crash

Issue - State: closed - Opened by gajus about 7 years ago - 1 comment

#6 - Destroy Chrome instance upon SIGINT

Issue - State: closed - Opened by gajus over 7 years ago - 4 comments

#5 - Chrome processes remain hanging after the program is shutdown

Issue - State: closed - Opened by gajus over 7 years ago - 1 comment

#4 - Add ability to configure browser window size