-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor to leverage Headless Chrome over PhantomJS #1
Comments
gingeleski
added a commit
to gingeleski/xssmap
that referenced
this issue
Mar 12, 2018
gingeleski
added a commit
to gingeleski/xssmap
that referenced
this issue
Mar 12, 2018
gingeleski
added a commit
to gingeleski/xssmap
that referenced
this issue
Mar 14, 2018
gingeleski
added a commit
to gingeleski/xssmap
that referenced
this issue
Mar 14, 2018
gingeleski
added a commit
to gingeleski/xssmap
that referenced
this issue
Mar 14, 2018
gingeleski
added a commit
to gingeleski/xssmap
that referenced
this issue
Mar 15, 2018
gingeleski
added a commit
to gingeleski/xssmap
that referenced
this issue
Mar 15, 2018
gingeleski
added a commit
to gingeleski/xssmap
that referenced
this issue
Mar 15, 2018
gingeleski
added a commit
to gingeleski/xssmap
that referenced
this issue
Mar 16, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the time we first wrote this (mid-2017), the field of headless browsing was surveyed to determine what we'd base the tool on. Headless Chrome was not yet mature enough to meet our needs and we focused on PhantomJS.
Now I believe that's no longer the case. It would be preferable for the tool to be based primarily on Headless Chrome.
This is something I intend to tackle in my fork during (currently sparse) downtime.
Related resources, for my reference and anyone interested in Headless Chrome:
The text was updated successfully, but these errors were encountered: