Dominicm, Your feedback is really helpful for us to improve the jQuery selector. I will look into the issues you listed here.
Thanks, Jian 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. > > 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". > > 3. The "disableJQuerySelector" method does not entirely disable > jQuery. It appears to create XPath selectors but they are still > prefixed with "jquery=". > > 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. > > 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. > > 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. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
