I've been bending my brain round that Javascript thing for a while and
should a glimmer of intelligence shine into the murk of my brain, I'll
certainly contribute any code I create towards a standard method for
dealing with these things...
Max Russell
Test Analyst.
INPS
Tel: 01382 223900
Agreed: http://jira.openqa.org/browse/WTR-121.
On 12/20/06, Charley Baker <[EMAIL PROTECTED]> wrote:
Ah, you're adding it to the IE class, which in Watir 1.4.1 was a super of
Frame. In 1.5.1, Frame doesn't inherit from IE, but does include Container
and PageContainer as mixins. You'll want to c
Is there any reason why the run_script method should not be added to the
main Watir distribution? Let's add a jira ticket for this, so it's on
our list.
___
Wtr-general mailing list
Wtr-general@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-ge
Ah, you're adding it to the IE class, which in Watir 1.4.1 was a super of
Frame. In 1.5.1, Frame doesn't inherit from IE, but does include Container
and PageContainer as mixins. You'll want to change your run_script method to
the Container namespace:
module Watir::Container
def run_script
...
I'm running the code on the same machine as I'm developing it...
The error I'm seeing is like this:
test_drag_and_drop(TestWatir):
NoMethodError: undefined method `run_script' for
#
dragdrophacking.rbw:40:in `test_drag_and_drop'
The code I'm trying to work is one I've posted
You're calling straight into the document ole object, Watir shouldn't be
doing anything but passing the call on to IE. What error are you getting?
Are you running the scripts on the same box with different version of Watir
and seeing it fail?
-Charley
On 12/20/06, Max Russell <[EMAIL PROTECTED]>
Has the support for executing javascript changed in 1.5?
A method I used previously:
def run_script(js)
ie.Document.parentWindow.execScript(js)
end
calling the execScript method no longer seems to work
Max Russell
Test Analyst.
INPS
Tel: 01382 223900
Fax: 01382
