Bret,
It looks to me like the following piece of code in watir.rb (after the
second method of the Watir module) is causing rdoc to stop parsing at
that point.
# add an error checker for http navigation errors, such as 404, 500 etc
NAVIGATION_CHECKER = Proc.new do |ie|
if ie.document.frames.length > 1
1.upto ie.document.frames.length do |i|
begin
ie.frame(:index, i).check_for_http_error
rescue Watir::Exception::UnknownFrameException
# frame can be already destroyed
end
end
else
ie.check_for_http_error
end
end
When I comment this out, rdoc seems to get everything.
Ethan
On 1/3/07, Bret Pettichord <[EMAIL PROTECTED]> wrote:
> Dave Munns wrote:
> > Thanks Brett, that worked! Is there documentation that describes the
> > arguments available for each object?
> >
> I was going to say that you could look at the rdoc for Watir::Element,
> but for some reason this is not being generated.
>
> If anyone knows how to debug RDOC problems, i'd appreciate any advice
> you could give. Specifically, no doc is being generated for
> Watir::Element or any of its subclasses. Other classes are not getting
> all their methods documented. Use "rake rdoc" to generate rdoc for our
> source. If you are using the gem, you can get the current (incomplete)
> rdoc from the gem rdoc server.
>
> Bret
> _______________________________________________
> 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
