[
http://jira.openqa.org/browse/WTR-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19922#action_19922
]
Jarmo Pertman commented on WTR-459:
-----------------------------------
There was indeed a bug with using #click_no_wait with frames caused by their
difference from other elements and not loading Watir::Frame class for
#click_no_wait process.
It will be fixed in 1.6.7, but you can fix it locally by adding
require "watir/frame"
into watir/core.rb right after require "page-container".
If this fixes your problem then it's good. If not, then check what other error
messages do you get when using $DEBUG = true.
It could be also possible that you'd need to edit Frame#attach_command as seen
from the commit link below.
Commit, which fixes the problem is seen here:
http://github.com/bret/watir/commit/5b942c7569c47155bb1d9ccbf3f5aa030e48a9da
> click_no_wait does not work in ruby 1.8.6 (2007-09-24 patchlevel 111)
> ---------------------------------------------------------------------
>
> Key: WTR-459
> URL: http://jira.openqa.org/browse/WTR-459
> Project: Watir
> Issue Type: Bug
> Components: Wait
> Affects Versions: 1.6.6
> Environment: ruby 1.8.6 (2007-09-24 patchlevel 111), Watir 1.6.6
> Reporter: problem_child
> Priority: Blocker
>
> click_no_wait is not working in ruby 1.8.6 (2007-09-24 patchlevel 111), Watir
> 1.6.6
> $frame.button(:name, "button1").click_no_wait
> =>nil
> If I use $frame.button(:name, "button1").click it works so it is finding the
> object.
> But using click_no_wait results in nill using IRB.
> An error is not reported otherwise.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.openqa.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Wtr-development mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-development
