Permalink
Commits on Mar 21, 2012
  1. Rename confusing method

    jferris committed Mar 21, 2012
  2. Keep a running command and a queued command instead of a running comm…

    …and and name/arguments
    jferris committed Mar 21, 2012
Commits on Mar 16, 2012
  1. Simplify Visit

    jferris committed Mar 16, 2012
  2. Add support for HTML input event (aka oninput) on text fields.

    The input event is like onchange, but on text fields, it is fired as soon as the value of the field changes, not when the field is blurred. It is a more appropriate event than 'keydown' or 'keyup', which behave unpredictably with paste events, held-down keys, etc.
    
    Support is a little problematic, but it is supported well by Webkit and Firefox, so it seems useful to add here.
    whatcould committed with halogenandtoast Feb 12, 2012
  3. Make the server bind to localhost. We don't really want to expose it …

    …to the world, and it pops up firewall warnings if you have an app aware firewall enabled (e.g. OSX firewall).
    raggi committed with halogenandtoast Feb 6, 2012
  4. Bump to 0.10.2

    halogenandtoast committed Mar 16, 2012
Commits on Mar 9, 2012
Commits on Mar 2, 2012
  1. Bump version to 0.10.1

    halogenandtoast committed Mar 2, 2012
Commits on Feb 27, 2012
  1. Fixed Installing QT link

    jferris committed Feb 27, 2012
Commits on Feb 24, 2012
Commits on Feb 17, 2012
  1. Commit Gemfile.lock

    halogenandtoast committed Feb 17, 2012
  2. Bump to version 0.10.0

    halogenandtoast committed Feb 17, 2012
Commits on Feb 12, 2012
  1. Fix destructive methods for selecting options

    Both `select_option` and `unselect_option` were modifying the
    `selected` attribute of their target `<option>` element. This attribute
    is meant to be used solely as the marker for which `<option>`(s) is
    (are) the default selection(s) in a (multi-)`<select>` element. The
    actual _selectedness_ of an `<option>` should be tracked using its
    `selected` **property**. Read [the spec][] for more info.
    
    This change removes any code which modified the `selected` attribute of
    `<option>` elements, which leaves only the code that modifies the
    `selected` property. In addition, `Node#value` needed to be changed to
    return `<option>` elements whose selectedness is true rather than just
    those with a `selected` attribute.
    
    The tests introduced in the previous commit now pass.
    
    [the spec]: http://dev.w3.org/html5/spec/Overview.html#the-option-element
    jasonmp85 committed Feb 12, 2012
  2. Add failing unit test for selected attribute bug

    capybara-webkit's driver implements `(un)select_option` by modifying
    the target node's `selected` attribute directly. The [HTML5 spec][]
    states that this attribute represents the _default selectedness_ of an
    `<option>` element, so modifying it will necessarily break the behavior
    of reset buttons in forms.
    
    In addition, the existing code leaves this attribute set on existing
    `<option>` elements, which can put the page into an invalid state.
    
    [HTML5 spec]: http://dev.w3.org/html5/spec/Overview.html#the-option-element
    jasonmp85 committed Feb 12, 2012
Commits on Feb 9, 2012
  1. Add note about Sinatra.

    gabebw committed Feb 9, 2012
Commits on Feb 5, 2012
Commits on Feb 3, 2012
  1. Update ChangeLog

    halogenandtoast committed Feb 3, 2012
  2. Bump to version 0.9.0

    halogenandtoast committed Feb 3, 2012
Commits on Jan 31, 2012