All Versions
35
Latest Version
Avg Release Cycle
77 days
Latest Release
2247 days ago

Changelog History
Page 4

  • v0.5 Changes

    ๐Ÿ”‹ Features
    • Detect if clicking an element will fail. If the click will actually hit another element (because that element is in front of the one we want to click), the user will now see an exception explaining what happened and which element would actually be targeted by the click. This should aid debugging. [Issue #25]
    • Click elements at their middle position rather than the top-left. This is presumed to be more likely to succeed because the top-left may be obscured by overlapping elements, negative margins, etc. [Issue #26]
    • ๐ŸŒ Add experimental support for using the remote WebKit web inspector. This will only work with PhantomJS 1.5, which is not yet released, so it won't be officially supported by Poltergeist until 1.5 is released. [Issue #31]
    • Add page.driver.quit method. If you spawn additional Capybara sessions, you might want to use this to reap the child phantomjs process. [Issue #24]
    • Errors produced by Javascript on the page will now generate an exception within Ruby. [Issue #27]
    • ๐Ÿ’Ž JRuby support. [Issue #20]
    ๐Ÿ› Bug fixes
    • Fix bug where we could end up interacting with an obsolete element. [Issue #30]
    • Raise an suitable error if PhantomJS returns a non-zero exit status. Previously a version error would be raised, indicating that the PhantomJS version was too old when in fact it did not start at all. [Issue #23]
    • โฑ Ensure the :timeout option is actually used. [Issue #36]
    • Nodes need to know which page they are associated with. Before this, if Javascript caused a new page to load, existing node references would be wrong, but wouldn't raise an ObsoleteNode error. [Issue #39]
    • In some circumstances, we could end up missing an inline element when attempting to click it. This is due to the use of getBoundingClientRect(). We're now using getClientRects() to address this.
  • v0.4 Changes

    • Element click position is now calculated using the native getBoundingClientRect() method, which will be faster and less buggy.
    • Handle window.confirm(). Always returns true, which is the same as capybara-webkit. [Issue #10]
    • 0๏ธโƒฃ Handle window.prompt(). Returns the default value, if present, or null.
    • Fix bug with page Javascript page loading causing problems. [Issue #19]
  • v0.3 Changes

    • There was a bad bug to do with clicking elements in a page where the page is smaller than the window. The incorrect position would be calculated, and so the click would happen in the wrong place. This is fixed. [Issue #8]
    • ๐ŸŒ Poltergeist didn't work in conjunction with the Thin web server, because that server uses Event Machine, and Poltergeist was assuming that it was the only thing in the process using EventMachine.

      To solve this, EventMachine usage has been completely removed, which has the welcome side-effect of being more efficient because we no longer have the overhead of running a mostly-idle event loop.

      [Issue #6]

    • ๐Ÿ”ง Added the :timeout option to configure the timeout when talking to PhantomJS.

  • v0.2 Changes

    • First version considered 'ready', hopefully fewer problems.
  • v0.1 Changes

    • First version, various problems.