Thanks for the clarification and apologies for the language. Cheers,
Alister Scott Brisbane, Australia On 19/04/2012, at 11:53 PM, Jari Bakken <jari.bak...@gmail.com> wrote: > You raise a valid point about the fact that we don't detect the loss > of focus, and that it leads to silent failures. Detecting this is a > hard problem, and if someone has time and knowledge to help out, we're > all ears. This is a specific problem though, not a general problem > with the IE driver. Adding the ability to run the IE driver with > synthesized events is something that's being actively worked on. It > would not entail a "rewrite" of the driver at all. > > When it comes to browser automation, I think we should focus on > working together to improve the WebDriver drivers whenever we find > issues. I'll actively work against adding support for watir-classic to > the watir-webdriver gem as long as I have a commit bit. > > For the record, I don't think the language you're using to describe > people's volunteer work is constructive. Especially when the person in > question is someone who has helped you personally on Twitter / Stack > Overflow, and in general bends over backwards to make the drivers as > good as possible. > > Jari > > On Wed, Apr 18, 2012 at 9:47 PM, Alister Scott <alister.sc...@gmail.com> > wrote: >> I've realized the hard way over the last few weeks that the technology in >> the IE WebDriver drivers is really shit. (I've been using C# but it's the >> same driver code underneath). For example, it continually doesn't perform >> actions when it loses focus, but doesn't complain, do future actions don't >> work. This is because it uses 'native' events which require 100% focus >> otherwise they think they work, but don't. >> >> So, I reckon Watir-webdriver should switch to the classic watir driver when >> controlling IE: and use webdriver drivers for everything else. >> >> That way it'd be a real differentiator: and we wouldn't lose all the great >> work Jarmo has done. >> >> And at some point the IE webdriver bindings need a rewrite to not use the >> native events. That way all the other languages C#, Java etc would get >> better IE support. >> >> Perhaps someone experienced in writing the original Watir IE driver can help >> Jim Evans to make it robust. >> >> Cheers, >> >> Alister Scott >> Brisbane, Australia >> >> On 18/04/2012, at 10:54 PM, "Željko Filipin" <zeljko.fili...@gmail.com> >> wrote: >> >> Hi everybody, >> >> We have talked about a few things at the Bazaar. I needed a few weeks to get >> back in track after returning home (the Bazaar was the end of more than two >> month long trip), but now I want to get things moving. >> >> I have a few questions. >> >> 1) What is the status of Watir 3.0? Are we releasing it soon? >> >> 2) I hope a few people will join me in updating Watir documentation (wiki, >> podcast...) in the next few weeks. The podcast has a new team, they have >> already released one episode: >> >> http://watirpodcast.com/ >> >> I remember a few people at the Bazaar said they would like to help. Should >> we create another list to communicate, or should we do it here? >> >> 3) I think the agreement was to move my Watir Book to Watir repository at >> Github. That means the book is no longer my personal project, but community >> project. I would change the license from the current creative commons to BSD >> (to be the same as Watir). I think I can do that because I am the only major >> contributor. (I did have a few minor contributions.) >> >> I would still reserve the right to accept or reject pull requests. That >> would also mean that I would no longer sell the book, but provide all >> formats for free and ask for donations for Watir project. I think we will >> get less money that way, but it is not all about the money, right? (I was >> selling 0,42 books per day since 2011-09-21. The date is few days since >> Watir Book 0.7 was released.) >> >> I think I had a few more things, but nothing comes to my mind right now. >> Will ask later when I remember. >> >> Željko >> -- >> watir.com/book - author >> >> _______________________________________________ >> Wtr-development mailing list >> Wtr-development@rubyforge.org >> http://rubyforge.org/mailman/listinfo/wtr-development >> >> >> _______________________________________________ >> Wtr-development mailing list >> Wtr-development@rubyforge.org >> http://rubyforge.org/mailman/listinfo/wtr-development > _______________________________________________ > Wtr-development mailing list > Wtr-development@rubyforge.org > http://rubyforge.org/mailman/listinfo/wtr-development _______________________________________________ Wtr-development mailing list Wtr-development@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-development
