Commits on Feb 10, 2009
  1. @bret
  2. @bret

    fix line endings

    bret committed Feb 10, 2009
Commits on Nov 6, 2008
  1. Tagging release to Rubyforge.

    bret committed Nov 6, 2008
  2. Update release process notes.

    bret committed Nov 6, 2008
  3. Update notes for 1.6.2

    bret committed Nov 6, 2008
  4. Updated versions 1.6.2.

    Changed the way the default browser setting is set, to avoid a problem reported on Mac. Previously it defaulted to IE, unless someone set it. Now it is set to a browser who's gem is actually installed.
    bret committed Nov 6, 2008
Commits on Nov 5, 2008
  1. Add release note.

    bret committed Nov 5, 2008
  2. Require 'active_support' instead of 'activesupport' so that you don't…

    … need to have the newer version installed.
    bret committed Nov 5, 2008
  3. Lowercase browser options.

    bret committed Nov 5, 2008
  4. one more whitespace test for completeness

    bret committed Nov 5, 2008
  5. Adding css file.

    charley committed Nov 5, 2008
  6. Release notes updated for 1.6.0 and 1.6.1

    bret committed Nov 5, 2008
  7. Adding button image and directory

    charley committed Nov 5, 2008
Commits on Nov 4, 2008
  1. Fix problem with prior patch: errors when accessing elements by :text…

    … and a regular expression. Repair whitespace test.
    bret committed Nov 4, 2008
  2. release notes for 1.6 -- in progress

    bret committed Nov 4, 2008
Commits on Oct 31, 2008
  1. Updating comments

    bret committed Oct 31, 2008
  2. Updated for Watir 1.6.1

    - Renamed old "watir-common" gem to be "commonwatir". This will prevent it from accidently being installed when you do "gem install watir"
    - Fixed toplevel rake clean/clobber targets
    - Update version numbers
    bret committed Oct 31, 2008
  3. Add toplevel rakefile with targets "gems" and "clean".

    You can now build all the gems with "rake gems" and they will show up in the gems directory.
    bret committed Oct 31, 2008
  4. Added automatic gem activation to fix problem reported by Tony. Root …

    …cause was that "require" will implicitly activate gems, but "autoload" will not.
    
    Details:
    
    Changes to Watir::Browser.support:
    - Arguments are now in hash format
    - Automatically autoloads library
    - Automatically activates gem if installed
    bret committed Oct 31, 2008
Commits on Oct 30, 2008
  1. dang loadpath

    bret committed Oct 30, 2008
  2. Reduce surface area of Browser interface.

    bret committed Oct 30, 2008
  3. Remove dead code (IE.quit).

    Update FireWatir::Firefox::VERSION to match the gem version. It was set as 1.1.1 in 1.2.1.
    bret committed Oct 30, 2008
  4. Include the firewatir gem when you install watir. (This was used to b…

    …uild 1.6.0)
    bret committed Oct 30, 2008
Commits on Oct 29, 2008
  1. Fix build-script error.

    bret committed Oct 29, 2008
  2. Renaming libraries

      require 'watir' -> require 'watir/ie'
      require 'watir/browser' -> require 'watir'
      
    (but because the new 'watir' library autoloads 'watir/ie' this should have no impact on users.)
    bret committed Oct 29, 2008
  3. Renaming libraries

      require 'watir' -> require 'watir/ie'
      require 'watir/browser' -> require 'watir'
      
    (but because the new 'watir' library autoloads 'watir/ie' this should have no impact on users.)
    bret committed Oct 29, 2008
  4. No commit message

    bret committed Oct 29, 2008
  5. test repair

    bret committed Oct 29, 2008