Thanks for sharing your story. It's a good example for why it is really hard to include solutions in error messages.
I did not realize that these warnings were bothering you. It is easy to suppress them.
Watir uses a Logger object to do the logging. By default, it set to warn, and this is a warn message. You could provide your own, customized logger to Watir or change the settings on the default one in play.
Something like
ie.logger.level = Logger::ERROR
might work.
For details, see http://www.ruby-doc.org/stdlib/libdoc/logger/rdoc/index.html
Let us know what works for you and we'll add it to the FAQ.
Bret
On 5/2/06, Paul Carvalho <
[EMAIL PROTECTED]> wrote:
Just for the record, none of the advice in this FAQ entry have helped me get rid of this error. =(
I'm not trying to navigate to a frame on another site, but the two outside (empty) frames are hosted on a separate resource web site. When I check the frames, I see the following output:
----
irb(main):128:0> ie.show_frames
there are 4 frames
frame index: 1 --Access Denied--frame index: 2 name: FooBar
frame index: 3 name: MainWindow
frame index: 4 --Access Denied--
=> 0..3
----
I get these "Access is Denied" warnings randomly when I click buttons and follow links in the 'MainWindow' frame. This frame is hosted on the same site, so I don't know why the warning messages keep appearing.
I've tried everything in the FAQ but to no avail:
1. Navigate directly to the subframe..
--> Not relevant. I'm not navigating to a different subframe.
2. Add host to the Trusted Sites list.
--> Did it. No effect. Warnings still appear.
3. Place entry in Hosts file.
--> Same as (2) - no effect.
4. Set IE to "Low" Security Level zone setting
--> Can't do it. Corporate Security Policy enforces a minimum "Medium" value, so I can never set it to "Low".
This is why I need to spend time figuring out how to write the UnitTest output to a file -- so I can eliminate all these annoying Warnings. I even tried launching ruby with a quiet verbose setting but it had no effect. I have been totally unable to suppress these warnings.
In the end I've come to live with them, but I can't help but think that there must be something that can be done in the code to suppress these Warnings. Unfortunately, I'm too focussed on testing and/or solving the scripting problems to figure out how to eliminate these errors. They're annoying but so are mosquitos in the summer time. Oh well.
Just thought you should know that the FAQ entry doesn't help me in my situation.
Paul.On 02/05/06, Bret Pettichord < [EMAIL PROTECTED]> wrote:I've changed this error message to say
"Access Denied, see http://wiki.openqa.org/display/WTR/FAQ#FAQ-Accessdeniedwhentryingtoaccessaframe "
Please rephrase this wiki page if you have a better suggestion for the advice people should get in this situation.
BretOn 5/2/06, Michael Bolton <[EMAIL PROTECTED]> wrote:It clearly helps some people. I wonder if the error message could include
the suggestion to add the server to the trusted site? (I'll volunteer to
help with the writing of it.)
---Michael B.
_______________________________________________
Wtr-general mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general
_______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
