836719f72e
The [IO/A spec][1] for `read` is as follows: > Read up to n bytes from the stream, or until the end of the stream > has been reached. [If] n is null, reads up to the block size of the > underlying device, or up to 1024 bytes if the block size is not > discernible. If n is not specified, this method always reads the > full stream until its end is reached. ... Since discovering the block size of the underlying device is non-trivial, we will just default to 1024. **NOTE** The initial implementation of `File::read()` saves the current (original) position, seeks to the beginning of the stream, `readAll`s to the end, and then resets to the original position. I think that this behavior is unexpected and should be changed--it should read from the current position to the end of the stream and stay there. The user should explicitly `seek` to the beginning of the stream when necessary. With the current implementation, the user should note that the position *will not change* after calling `read()` with no arguments. [1]: http://wiki.commonjs.org/wiki/IO/A#Instance_Methods http://code.google.com/p/phantomjs/issues/detail?id=938 |
||
|---|---|---|
| deploy | ||
| examples | ||
| rpm | ||
| src | ||
| test | ||
| tools | ||
| website | ||
| .gitignore | ||
| CONTRIBUTING.md | ||
| ChangeLog | ||
| LICENSE.BSD | ||
| README.md | ||
| build.sh | ||
| phantomjs.pro | ||
| third-party.txt | ||
README.md
PhantomJS - Scriptable Headless WebKit
PhantomJS (www.phantomjs.org) is a headless WebKit scriptable with JavaScript or CoffeeScript. It is used by hundreds of developers and dozens of organizations for web-related development workflow.
The latest stable release is version 1.8 (codenamed "Blue Winter Rose"). Follow the official Twitter stream @PhantomJS to get the frequent development updates.
Note: Please do not create a GitHub pull request without reading the Contribution Guide first. Failure to do so may result in the rejection of the pull request.
Use Cases
- Headless web testing. Lightning-fast testing without the browser is now possible! Various test frameworks such as Jasmine, Capybara, QUnit, Mocha, WebDriver, YUI Test, BusterJS, FuncUnit, Robot Framework, and many others are supported.
- Page automation. Access and manipulate web pages with the standard DOM API, or with usual libraries like jQuery.
- Screen capture. Programmatically capture web contents, including CSs, SVG and Canvas. Build server-side web graphics apps, from a screenshot service to a vector chart rasterizer.
- Network monitoring. Automate performance analysis, track page loading and export as standard HAR format.
Features
- Multiplatform, available on major operating systems: Windows, Mac OS X, Linux, other Unices.
- Fast and native implementation of web standards: DOM, CSS, JavaScript, Canvas, SVG. No emulation!
- Pure headless (no X11) on Linux, ideal for continuous integration systems. Also runs on Amazon EC2, Heroku, Iron.io.
- Easy to install: Download, unpack, and start having fun in just 5 minutes.
Ecosystem
PhantomJS needs not be used only as a stand-alone tool. Check also some excellent related projects:
- CasperJS enables easy navigation scripting and common high-level testing.
- Poltergeist allows running Capybara tests headlessly.
- Guard::Jasmine automatically tests Jasmine specs on Rails when files are modified.
- GhostDriver complements Selenium tests with a PhantomJS WebDriver implementation.
- PhantomRobot runs Robot Framework acceptance tests in the background via PhantomJS.
- Mocha-PhantomJS run Mocha tests using PhantomJS.
and many others related projects.
Questions?
- Explore the complete documentation
- Read tons of user articles on using PhantomJS.
- Join the mailing-list and discuss with other PhantomJS fans.
PhantomJS is free software/open source, and is distributed under the BSD license. It contains third-party code, see the included third-party.txt file for the license information on third-party code.
PhantomJS is created and maintained by Ariya Hidayat (Twitter: @ariyahidayat), with the help of many contributors.