On Tue, Jan 17, 2012 at 9:49 PM, Hugh McGowan <[email protected]> wrote:
> Also Jarmo, is there a reason we're hard-coding the watirspec to a change > number? Seems like we'd be better off to just let watirspec:init get the > latest. I'm working through the IE9 issues now so between updating tests > and adding some code changes we should be able to get IE8 and IE9 to the > same level of support. I have understood that the point with git submodules is to have same version for everyone. I'm not sure though. Seeing Button#click to fail for you make sure you're using latest Sinatra. I was having failures with tests which were accessing http://localhost:2000with older Sinatra since newer Sinatra has "public_folder" as an option for static content instead of "public" and WatirSpec uses "public_folder" as an option. Thanks for the work with IE9! Seeing IE9 failures i'm thinking that you need to add new guard for IE9 so you could use "not_compliant_on" and "deviates_on" guards in specs. Jarmo
_______________________________________________ Wtr-development mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-development
