[wtr-general] Re: Watir 2.0.0.rc2 released
These problems should now be fixed in version 2.0.1
Jarmo
On Aug 10, 6:29 pm, Jarmo Pertman jarm...@gmail.com wrote:
Thanks.
The next release will try to focus for Ruby 1.9.2. I suspect that this
problem is related with the browser.close problem in 1.9.2 too.
Jarmo
On Aug 9, 10:14 pm, Dmitriy Korobskiy dkro...@gmail.com wrote:
On 7/27/11 11:02 AM, Jarmo Pertman wrote:
Don't use Ruby 1.9.2 right now since it is related with other bugs
related
with 1.9.2. Didn't want to fix those at the moment to avoid even bigger
changes.
Jarmo
I found one regression where the code works in Watir 2.0.0.rc3/Ruby
1.8.x, but stops working in Ruby 1.9.x.
Just want to report it, so you can add it to the list if it has not been
reported before. BTW, it works in Watir 1.9.2/Ruby 1.9.x.
The regression is in links() collection and link() locators: they
apparently stop working. The following code should
dump a bunch of links. In Watir 2.0.0.rc3/1.9.x, links() collection is
returned empty.
# Windows only
#
require 'watir'
browser = Watir::IE.new_window
browser.goto(http://google.com;)
if browser.url.include?(google.com)
puts Navigated to Google
end
for link in browser.links
puts #{link.text} #{link.to_s}
end
begin
browser.close
rescue = e
puts WARNING: Error in closing the
browser:\n#{e.message}\n#{e.backtrace}
end
--
DK
AIM: DKroot1, Skype: DKroot
--
Before posting, please read http://watir.com/support. In short: search before
you ask, be nice.
watir-general@googlegroups.com
http://groups.google.com/group/watir-general
watir-general+unsubscr...@googlegroups.com
Re: [wtr-general] Re: Watir 2.0.0.rc2 released
On 8/11/11 5:46 AM, Jarmo Pertman wrote:
These problems should now be fixed in version 2.0.1
Jarmo
Yep, they are fixed. Thanks a bunch!
On Aug 10, 6:29 pm, Jarmo Pertmanjarm...@gmail.com wrote:
Thanks.
The next release will try to focus for Ruby 1.9.2. I suspect that this
problem is related with the browser.close problem in 1.9.2 too.
Jarmo
On Aug 9, 10:14 pm, Dmitriy Korobskiydkro...@gmail.com wrote:
On 7/27/11 11:02 AM, Jarmo Pertman wrote:
Don't use Ruby 1.9.2 right now since it is related with other bugs related
with 1.9.2. Didn't want to fix those at the moment to avoid even bigger
changes.
Jarmo
I found one regression where the code works in Watir 2.0.0.rc3/Ruby
1.8.x, but stops working in Ruby 1.9.x.
Just want to report it, so you can add it to the list if it has not been
reported before. BTW, it works in Watir 1.9.2/Ruby 1.9.x.
The regression is in links() collection and link() locators: they
apparently stop working. The following code should
dump a bunch of links. In Watir 2.0.0.rc3/1.9.x, links() collection is
returned empty.
# Windows only
#
require 'watir'
browser = Watir::IE.new_window
browser.goto(http://google.com;)
if browser.url.include?(google.com)
puts Navigated to Google
end
for link in browser.links
puts #{link.text} #{link.to_s}
end
begin
browser.close
rescue = e
puts WARNING: Error in closing the
browser:\n#{e.message}\n#{e.backtrace}
end
--
DK
AIM: DKroot1, Skype: DKroot
--
DK
AIM: DKroot1, Skype: DKroot
--
Before posting, please read http://watir.com/support. In short: search before
you ask, be nice.
watir-general@googlegroups.com
http://groups.google.com/group/watir-general
watir-general+unsubscr...@googlegroups.com
[wtr-general] Re: Watir 2.0.0.rc2 released
Thanks.
The next release will try to focus for Ruby 1.9.2. I suspect that this
problem is related with the browser.close problem in 1.9.2 too.
Jarmo
On Aug 9, 10:14 pm, Dmitriy Korobskiy dkro...@gmail.com wrote:
On 7/27/11 11:02 AM, Jarmo Pertman wrote:
Don't use Ruby 1.9.2 right now since it is related with other bugs related
with 1.9.2. Didn't want to fix those at the moment to avoid even bigger
changes.
Jarmo
I found one regression where the code works in Watir 2.0.0.rc3/Ruby
1.8.x, but stops working in Ruby 1.9.x.
Just want to report it, so you can add it to the list if it has not been
reported before. BTW, it works in Watir 1.9.2/Ruby 1.9.x.
The regression is in links() collection and link() locators: they
apparently stop working. The following code should
dump a bunch of links. In Watir 2.0.0.rc3/1.9.x, links() collection is
returned empty.
# Windows only
#
require 'watir'
browser = Watir::IE.new_window
browser.goto(http://google.com;)
if browser.url.include?(google.com)
puts Navigated to Google
end
for link in browser.links
puts #{link.text} #{link.to_s}
end
begin
browser.close
rescue = e
puts WARNING: Error in closing the
browser:\n#{e.message}\n#{e.backtrace}
end
--
DK
AIM: DKroot1, Skype: DKroot
--
Before posting, please read http://watir.com/support. In short: search before
you ask, be nice.
watir-general@googlegroups.com
http://groups.google.com/group/watir-general
watir-general+unsubscr...@googlegroups.com
Re: [wtr-general] Re: Watir 2.0.0.rc2 released
On 7/27/11 11:02 AM, Jarmo Pertman wrote:
Don't use Ruby 1.9.2 right now since it is related with other bugs related
with 1.9.2. Didn't want to fix those at the moment to avoid even bigger
changes.
Jarmo
I found one regression where the code works in Watir 2.0.0.rc3/Ruby
1.8.x, but stops working in Ruby 1.9.x.
Just want to report it, so you can add it to the list if it has not been
reported before. BTW, it works in Watir 1.9.2/Ruby 1.9.x.
The regression is in links() collection and link() locators: they
apparently stop working. The following code should
dump a bunch of links. In Watir 2.0.0.rc3/1.9.x, links() collection is
returned empty.
# Windows only
#
require 'watir'
browser = Watir::IE.new_window
browser.goto(http://google.com;)
if browser.url.include?(google.com)
puts Navigated to Google
end
for link in browser.links
puts #{link.text} #{link.to_s}
end
begin
browser.close
rescue = e
puts WARNING: Error in closing the
browser:\n#{e.message}\n#{e.backtrace}
end
--
DK
AIM: DKroot1, Skype: DKroot
--
Before posting, please read http://watir.com/support. In short: search before
you ask, be nice.
watir-general@googlegroups.com
http://groups.google.com/group/watir-general
watir-general+unsubscr...@googlegroups.com
[wtr-general] Re: Watir 2.0.0.rc2 released
There are known issues with Ruby 1.9.2 which i'd like to fix in the next version - e.g. 2.0.1. In the meantime, use 1.8.7. Jarmo On Jul 25, 8:39 pm, Chuck van der Linden sqa...@gmail.com wrote: So just to be clear, at this point for Watir 2.0.0 what would be our 'recommended' version of Ruby, and which versions would be 'supported'? (in that context I consider: 'supported' = should work, may have been tested; 'recommended' = 'tested' and likely to work 'best' and/or used by watir developers.) On Jul 25, 5:03 am, Jarmo jarm...@gmail.com wrote: Don't use Ruby 1.9.2 right now since it is related with other bugs related with 1.9.2. Didn't want to fix those at the moment to avoid even bigger changes. Jarmo On Mon, Jul 25, 2011 at 2:59 PM, Alister Scott alister.sc...@gmail.comwrote: I am having a play around with this on Win7/Ruby 1.9.2, but can't get very far. What am I doing wrong? irb(main):001:0 require 'watir' = true irb(main):002:0 b = Watir::Browser.new = #Watir::IE:0x..f90492b14 url=about:blank title= irb(main):003:0 b.goto 'www.google.com' = 1.363929 irb(main):004:0 b.text_field(:name = q).set s NoMethodError: unknown property or method: `createEvent' HRESULT error code:0x80020006 Unknown name. from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-2.0.0.rc2/lib/watir/element.rb:37 7:in `method_missing' from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-2.0.0.rc2/lib/watir/element.rb:37 7:in `create_event' from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-2.0.0.rc2/lib/watir/element.rb:34 3:in `dispatch_event' from C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-2.0.0.rc2/lib/watir/input_element s.rb:376:in `set' from (irb):4 from C:/Ruby192/bin/irb:12:in `main' irb(main):005:0 Cheers, Alister Scott Brisbane, Australia Watir Web Master:http://watir.com Blog:http://watirmelon.com LinkedIn:http://www.linkedin.com/in/alisterscott There are two ways to get enough: One is to continue to accumulate more and more. The other is to desire less. *~ G. K. Chesterton* On Mon, Jul 25, 2011 at 8:59 PM, Jari Bakken jari.bak...@gmail.comwrote: On Sun, Jul 24, 2011 at 11:53 PM, Jarmo jarm...@gmail.com wrote: Good news everyone! I've found some time to play with Watir and managed to release a new version - 2.0.0.rc2 (rc1 had buggy dependency, sorry)! There are some big changes including 0-based-indexing, which is enabled by default and not releasing new versions of FireWatir. Also, all collection factory methods accept now (multiple) specifiers/locators. A lot of these changes are compatible with Watir-WebDriver (see the list of incompatibilities compared with previous versions Nice work! * renamed CheckBox class to Checkbox * renamed CheckBoxes class to Checkboxes What's the rationale for this? This adds a new incompatibility with watir-webdriver and breaks backwards compatibility for anyone relying on the class name. The change seems rather arbitrary. Jari -- Before posting, please readhttp://watir.com/support. In short: search before you ask, be nice. watir-general@googlegroups.com http://groups.google.com/group/watir-general watir-general+unsubscr...@googlegroups.comhttp://groups.google.com/group/watir-general%0Awatir-general+unsubscr... ___ Wtr-development mailing list wtr-developm...@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-development -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. watir-general@googlegroups.com http://groups.google.com/group/watir-general watir-general+unsubscr...@googlegroups.com
[wtr-general] Re: Watir 2.0.0.rc2 released
On Jul 25, 9:02 pm, Chuck van der Linden sqa...@gmail.com wrote: I presume the dropping of FireWatir is due to issues with a lack of JSSH extensions for current versions? We might want to say something specific in that regard in the release notes, and direct Firefox users to Watir-Webdriver. (otherwise people new to the party may be confused and think we've all been co-opted by MS, force-fed 'IE- Koolaid' or something similar. After all, if you don't know the 'why' dropping firewatir seems on the surface of it, kinda insane. Yes, it's due to JSSH extension. Good idea, we should point it out in the changelog. Will do before release. One request for anyone working on updating the docs such as the supported elements table (http://wiki.openqa.org/display/WTR/HTML +Elements+Supported+by+Watir), it might make sense at this point to 'archive' the existing watir 1.x page as is with a v1 tacked onto the end of the URL. Place headers on both pages indicating the 'as of' version for the docs, and a link to the old/new version respectively. That would make it easier for anyone hanging back to find appropriate docs. If someone who knows the wiki stuff better than I can create the 'archive' page, I might be able to find time this week to take a hack at updating that doc (which is one I always find highly useful) for the v2 version. (since I have a bit more free time at the moment due to being between employers) And yes, docs should be updated. You can mark all elements (except new browser window) with a checkbox for multiple attributes, :xpath and :css for sure. Jarmo -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. watir-general@googlegroups.com http://groups.google.com/group/watir-general watir-general+unsubscr...@googlegroups.com
[wtr-general] Re: Watir 2.0.0.rc2 released
On Jul 25, 1:59 pm, Jari Bakken jari.bak...@gmail.com wrote: * renamed CheckBox class to Checkbox * renamed CheckBoxes class to Checkboxes What's the rationale for this? This adds a new incompatibility with watir-webdriver and breaks backwards compatibility for anyone relying on the class name. The change seems rather arbitrary. Oh crap! The rationale behind that is that there is TextField = browser.text_field and there is ChecBox = browser.checkbox... it just seems to be wrong there... also, i looked at https://github.com/jarib/watir-webdriver/tree/master/lib/watir-webdriver/elements and noticed there checkbox.rb and assumed that there is a Checkbox class in Watir-WebDriver (because of the filename). I guess you should rename that file at least :) I will revert back the rename change if that's not compatible with Watir-WebDriver, thanks for pointing that out! Jari Jarmo -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. watir-general@googlegroups.com http://groups.google.com/group/watir-general watir-general+unsubscr...@googlegroups.com
[wtr-general] Re: Watir 2.0.0.rc2 released
On Jul 24, 2:53 pm, Jarmo jarm...@gmail.com wrote: Good news everyone! I've found some time to play with Watir and managed to release a new version - 2.0.0.rc2 (rc1 had buggy dependency, sorry)! There are some big changes including 0-based-indexing, which is enabled by default and not releasing new versions of FireWatir. Also, all collection factory methods accept now (multiple) specifiers/locators. A lot of these changes are compatible with Watir-WebDriver (see the list of incompatibilities compared with previous versions athttps://github.com/jarib/watir-webdriver/wiki/Comparison-with-Watir-1.X). details snipped Cheers! Jarmo Pertman This is cool stuff. I presume the dropping of FireWatir is due to issues with a lack of JSSH extensions for current versions? We might want to say something specific in that regard in the release notes, and direct Firefox users to Watir-Webdriver. (otherwise people new to the party may be confused and think we've all been co-opted by MS, force-fed 'IE- Koolaid' or something similar. After all, if you don't know the 'why' dropping firewatir seems on the surface of it, kinda insane. One request for anyone working on updating the docs such as the supported elements table (http://wiki.openqa.org/display/WTR/HTML +Elements+Supported+by+Watir), it might make sense at this point to 'archive' the existing watir 1.x page as is with a v1 tacked onto the end of the URL. Place headers on both pages indicating the 'as of' version for the docs, and a link to the old/new version respectively. That would make it easier for anyone hanging back to find appropriate docs. If someone who knows the wiki stuff better than I can create the 'archive' page, I might be able to find time this week to take a hack at updating that doc (which is one I always find highly useful) for the v2 version. (since I have a bit more free time at the moment due to being between employers) -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. watir-general@googlegroups.com http://groups.google.com/group/watir-general watir-general+unsubscr...@googlegroups.com
