Hi
After some more digging around this is what I could figure
This is what the XPath that I get from xpather :
/html/body/d...@id='maincontainer']/d...@id='contentwrapper']/fo...@id='j_id5']/table/tbody/tr/t...@class='listRight'
and
position()=2]/sp...@id='j_id5:dietDiaryPanel']/d...@id='j_id5:calendarmessages']/
*...@class='font_underline' and @id='j_id5:calendarmessages:here']
*When I have
ui.TextBox(uid:"here",clocator:[id:"%%:here"])
I am able to get true for isElementPresent("here") . But I am unable to do a
click .
When I have
ui.UrlLink(uid:"here",clocator:[id:"%%:here"])
I get false for isElementPresent("here"). Not sure why is happenning
How do get click implemented on the Textbox ?
Regards
Hari
On Sat, Feb 28, 2009 at 10:03 AM, John <[email protected]> wrote:
>
> Could you look at the log to see what the xpath the isElementpresent
> ("xxx") command
> generated? Then, look it up in the XPather inside the DOM inspector?
>
> Thanks,
>
> Jian
>
> On Feb 27, 11:10 pm, Harihara Vinayakaram <[email protected]> wrote:
> > Hi
> > That is the strange problem. Firebug shows that the element is present
> .
> > Trump shows that the element is present. When I view the element in the
> > browser as part of the Selenium test it is also there. Printing getText
> of
> > the parent in my test case also prints the text of this element.
> >
> > But a isElementpresent("xxx") shows false
> >
> > But my test case does not find it. I have a simple
> > UrlLink(uid:"xxx", clocator[tag:"a", id:"%%:here"])
> >
> > The only thing is that this is refreshed as part of an Ajax action . I
> am
> > able to find other elements which are refreshed by the DOM action but
> this
> > particular element is proving elusive
> >
> > Hence the question
> > Regards
> > Hari
> >
> > On Sat, Feb 28, 2009 at 9:03 AM, John <[email protected]> wrote:
> >
> > > Why not use some tools such as Firebug or DOM inpsector. For example,
> > > in the DOM inspector,
> > > you can select a web element by click and then use: right click > Copy
> > > XML to get the DOM structure
> > > or you can browse it on the UI view there.
> >
> > > Thanks,
> >
> > > Jian
> >
> > > On Feb 27, 10:29 pm, Harihara Vinayakaram <[email protected]> wrote:
> > > > Hi
> > > > I have been having some wierd problems with respect to Frames and
> some
> > > > elements. Most of my debugging efforts have not gone anywhere. Is
> there a
> > > > method by which I can print the current DOM . I know there is a
> method to
> > > > print the HTML page. I do not want that. I want to see if I can print
> the
> > > > DOM structure
> >
> > > > Regards
> > > > Hari
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"tellurium-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/tellurium-users?hl=en
-~----------~----~----~----~------~----~------~--~---
