[wtr-general] Re: show_frames not reading nested frames properly

Wed, 23 Sep 2009 22:13:47 -0700 

>> br = FireWatir::Firefox.new
=> #<FireWatir::Firefox:0x10212aec8 @window_title="",
@t=#<Thread:0x10212add8 sleep>, @error_checkers=[],
@window_url="about:blank">

>> br.frame(:index, 1).text
=> "<!--//--><![CDATA[//><!-- var cm_role = \"live\"; var cm_host = \"
angelfire.lycos.com\"; var cm_taxid = \"/memberembedded\"; var
angelfire_member_name = \"super/badwebs\"; var angelfire_member_page =
\"super/badwebs/top.htm\"; var angelfire_ratings_hash =
\"1253768558:386929fd16af6080283e9ca8a28ebfa9\"; var lycos_ad_category =
{\"dmoz\":\"arts\\/animation\",\"ontarget\":\"&CAT=family%20and%20lifestyles&L2CAT=hobbies\"};
var lycos_ad_remote_addr = \"58.28.124.70\"; var lycos_ad_www_server = \"
www.angelfire.lycos.com\"; var edit_site_url = \"
www.angelfire.lycos.com/landing/landing.tmpl?utm_source=house&utm_medium=landingpage&utm_campaign=toolbarlink\";
var lycos_ad_track_small = \"
http://www.angelfire.com/doc/images/track/ot_smallframe.gif?rand=817133\";;
var lycos_ad_track_served = \"
http://www.angelfire.com/doc/images/track/ot_adserved.gif?rand=817133\";;
//--><!]]> <img src=\"
http://www.angelfire.com/doc/images/track/ot_noscript.gif?rand=817133\";
alt=\"\" width=\"1\" height=\"1\" /> <!-- BEGIN STANDARD TAG - 728 x 90 -
Lycos - Angelfire Fallthrough - DO NOT MODIFY --> <iframe frameborder=\"0\"
marginwidth=\"0\" marginheight=\"0\" scrolling=\"no\" width=\"728\"
height=\"90\" src=\"
http://ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=280303\";></iframe>
<!-- END TAG --> The World's Worst Website Thanks for Stopping By!"

>> br.frame(:name, 'contents').p(:index, 1).text
=> "Gratuitous use of frames is a common mistake of web designers."

So it works in this case. I'll have to try locating that frame using :index
perhaps.
--
Rafael Fonseca
www.nunca.com.br


2009/9/24 Alan Baird <[email protected]>

> Rafael -
> I'm curious why the page you are showing us is a page you get when you
> can't see frames.  Maybe that's just an example, but I wonder if that is
> interfering w/ Watir.
>
> If you want to try some things out, I have an example for you.  Go to
> http://www.angelfire.com/super/badwebs/ (it's safe, but an ugly website -
> first useable thing that came up in Google), open up irb (or watir-console
> like I do) and do the following:
>
> >>br = Watir::IE.attach(:url, /angelfire/)
> >> br.frame(:index, 1).text
> => "The World's Worst WebThe World's Worst Website   \r\nThanks for
> Stopping By!"
> >> br.frame(:name, 'contents').p(:index, 1).text
> => "Gratuitous use of frames is a common mistake of web designers."
>
> This is what I got when I ran the commands on this site.  Hopefully you get
> the same.  If so, maybe it will give you some more ideas on how to
> troubleshoot your specific site.
>
> Alan
>
> On Tue, Sep 22, 2009 at 3:16 AM, Rafael Fonseca <[email protected]>wrote:
>
>> Thanks for the reply.
>> But I've been through that and similar pages describing how to access
>> frames, and they're very sparse on the issue. I still can't figure out why
>> the frameset doesn't get read by Watir.
>>  --
>> Rafael Fonseca
>> www.nunca.com.br
>>
>> On 22/09/2009, at 8:11 PM, Željko Filipin wrote:
>>
>> On Tue, Sep 22, 2009 at 6:25 AM, magu <[email protected]> wrote:
>> > Any tips to why this happen or workarounds or even where to read more
>> > about this would be greatly appreciated.
>>
>> http://wiki.openqa.org/display/WTR/Frames
>>
>> Željko
>> --
>> http://watirpodcast.com/
>>
>>
>>
>>
>>
>>
>>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Watir General" group.
To post to this group, send email to [email protected]
Before posting, please read the following guidelines: 
http://wiki.openqa.org/display/WTR/Support
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/watir-general
-~----------~----~----~----~------~----~------~--~---

Reply via email to