Retina screens for every Mac.
A new Mac Pro. Finally.
Air Drop support across the Internet and not just your local network.
Pull all the Google-centric code from WebKit 2 and make the next version of Safari suck less. No more reloading all my tabs please.
The ability to read your iBooks on your Mac.
MapKit for OS X.
Siri support for the Mac.
No pressure, right?
If you're using the WebKit formatter, or any other formatter for that matter, add this to the @.tm_properties@ either in your $HOME (to apply it to all RSpec bundle output), or in a specific project's @.tm_properties@ file:
I'm excited about the possibilities of tweaking the editor's behavior on a directory-by-directory basis.
…create screenshots of the graphs is to use PhantomJS , which is a headless WebKit with an that has support for taking screenshots.
We also have the following requirements for our report emails:
Don't generate the Mini-Pulse if the email is never opened , to conserve server resources
Cache the generated image once the email was opened once
Securely serve the image and use encrypted URLs with embedded authentication (the user the email was sent to may no longer have …
…:webkit if you want to choose the driver on a per scenario / describe basis. The same applies to @in .
If you're on, when you first run tests using capybara-webkit the OS X firewall might go a little crazy since it works by connecting over a socket. Just approve it and you're on your way.
You may also have issues if you're using transaction fixtures. If so, read the " Transactional Fixtures" section of the Capybara README.
…parity with WebKit. Let's follow this to its logical conclusion: In a world in which WebKit is now virtually the only mobile browser vendor Mozilla and Microsoft will feel increased pressure to switch their browser engines over to WebKit in order to keep pace. Google has proved that with Chrome that WebKit stagnation is simply a choice so there's no reason why these other companies shouldn't be able to build off of WebKit (and possibly create WebKit hybrids, such …
The ability of the browser to optimize the order, priority, and latency of each network resource is one of the most critical contributors to the overall user experience. You may not be aware of it, but Chrome's network stack is, quite literally, getting smarter every day, …
Thank you to Bill Joy, Bram Moolenaar, and Tim Pope for making and improving Vim, our beloved text editor.
Thank you to the many Postgres committers for a rock-solid and always-improving database.
Capybara Webkit is a Capybara driver for headless WebKit so you can test web apps.
Allows you to run yourtests on a popular and powerful headless WebKit browser: .
ClientSideValidations extracts the validations from yourmodels and applies them to your forms directly on the client. 3.2 brings quite a few changes and extras, such as support for Rails 4.0's feature.
TomDoc Package for…
Cue PhantomJS , a headless WebKit browser designed for page automation and testing. When coupled with SinonJS spies and the Mocha testing framework the difference between testing a single page and twenty at a time became marginal.
I'd like to go over these technologies in detail and provide a basic tutorial of our methodology.
What is a headless browser?
runs without a graphic interface. It can navigate as if it …