On Mon, Nov 2, 2009 at 10:01 AM, Ethan <[email protected]> wrote: > Container#element and #elements is supported in my branch. >
Right, there is a lot of stuff in your branch. Would it be possible for you to pull it out into feature branches to facilitate review? > Zero-based indexing, sounds good. I assume this would apply to subscripting > element collections, (ie, container.divs[0] instead of container.divs[1]); > would it also apply to container.div(:index, 0) rather than > container.div(:index, 1)? > http://jira.openqa.org/browse/WTR-61 BTW, one of the things that I've noticed is that many of the discussions about jira tickets never get recorded there and therefore get repeated a lot. I'm wondering if in the end this is really a problem with Jira. I noticed that in my recent use of Lighthouse, this didn't happen nearly as much. I think that tool made it easier to forward emails to the ticket and also encouraged people to post questions, etc in the ticket itself, partly because people could be set up as watching the ticket and thus get emails when ever someone added a comment. display_value, what's this? can you link to documentation or source? I'm not > seeing this with a quick search. > Good question. Here is what I'm talking about. http://github.com/bret/watircraft/blob/master/lib/extensions/watir.rb What would change with table and radio? > My email is really a followup to a number of ideas that I posted in this thread. http://rubyforge.org/pipermail/wtr-development/2009-October/001195.html -- Bret Pettichord Lead Developer, Watir, www.watir.com Blog, www.io.com/~wazmo/blog <http://www.io.com/%7Ewazmo/blog> Twitter, www.twitter.com/bpettichord
_______________________________________________ Wtr-development mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-development
