Hi John,
1. For the Infinity sign, Selenium does return "?" but when I convert
this to a double, it correctly returns Infinity.
2. The above was noticed because of the "position" problem. Here is
part of my uiObject
ontainer(uid:'runnerSummary',clocator:[tag:'table']){
Selector(uid:'runnerSelect', clocator:[id:'myBetsBetView'])
Div(uid:'totalMatched',clocator:[tag:'span',position:'2'])
Div(uid:'runnerMatched',clocator:[tag:'span',position:'3'])
Div(uid:'lastMatched',clocator:[tag:'span',position:'4'])
Div(uid:'projectedBsp',clocator:[tag:'span',position:'5'])
}
For jQuery to work I have to take 1 from all of the position numbers,
i.e.
ontainer(uid:'runnerSummary',clocator:[tag:'table']){
Selector(uid:'runnerSelect', clocator:[id:'myBetsBetView'])
Div(uid:'totalMatched',clocator:[tag:'span',position:'1'])
Div(uid:'runnerMatched',clocator:[tag:'span',position:'2'])
Div(uid:'lastMatched',clocator:[tag:'span',position:'3'])
Div(uid:'projectedBsp',clocator:[tag:'span',position:'4'])
}
3. I'm using multiople uiObjects in most of my tests. If I have
disableJQuerySelector in one and useJQuerySelector in another, this
causes conflicts. Depending upon which is defined first, I get either:
jquery selector called without "jquery=" prefix or
XPath selector called with "jquery=" prefix.
Any uiObjects that do not use either method correctly use XPath
selectors.
4. I think it is possible to use a wildcard for an id if it is
accessed as an attribute rather that using #.
5. I think this problem is due to the fact that XPath selectors use
"descendant-or-self", which is not really the same (as I understand
it) to " *", which is just "descendant". I've worked around the
problem in the following way.
Table was defined as follows:
Table(uid:'marketDepth', clocator:[class:'GlobalTableBorder'],
group:'true'){
Button(uid:"row:1, column:1",clocator:[name:'acceptButton'])
TextBox(uid:'all')
}
Removing the TextBox element fixed this problem. Not sure how this may
affect some of my other tables.
On Apr 16, 2:11 pm, John <[email protected]> wrote:
> Dominicm,
>
> I need more information from you, please see my reply inline.
>
> On Apr 16, 7:40 am, dominicm <[email protected]> wrote:> Hi,
>
> > First of all, I've sorted my perf issues and jQuery is looking very
> > worthwhile. Thanks to all involved.
>
> > A few issues I've noticed
> > 1. One of my text elements may contain an infinity sign. When I use
> > getText using jQuery it returns "?".whereas XPath would return
> > "\u221E". Not sure if this is simply a display thing.
>
> I suspect this is really caused by the json converter. From your log,
> you should
> be able to see what you get back from selenium before tellurium does
> jsonify.
> Could you post what you get back from selenium?
>
> > 2. Table cell numbering appears to be out of sync. jQuery is using an
> > index while XPath is using numbering. Although this seems to be taken
> > care of for default table operations, it causes problems when using
> > "position".
>
> Right, jquery uses index starting from zero while xpath uses position
> starting from 1.
> What do you mean: it causes problems when using "position"?
>
> > 3. The "disableJQuerySelector" method does not entirely disable
> > jQuery. It appears to create XPath selectors but they are still
> > prefixed with "jquery=".
>
> Could you list what methods you called when disableJQuerySelector
> did not work properly so that I can narrow down the errors?
>
> > 4. jQuery throws an error when it encounters a wildcard in an id. It
> > seems to use "#" as the default for ids, which does not like the %%
> > wildcard.
>
> Yes, # is the id identifier. I do not think jQuery allow partial
> matching ids.
> Mikhail, please correct me if I am wrong.
>
> > 5. For a table where there is no data in a cell, jQuery returns an
> > error as it cannot find any child elements of the table cell. XPath
> > returns null.
>
> Which way is preferable for you? We may need to hack into Selenium
> core
> to find the problem.
>
> > One of my tables is refusing to play the game with jQuery. This is
> > probably some of the worst HTML code that I've ever seen though, so
> > not entirely surprising. I'll try to debug and find out what is wrong.
>
> Please keep us posted about what you find.
>
> Thanks,
>
> Jian
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
