Mikhail, I would like to still keep clocator and it is good for some browsers such as Firefox. We can create a new locator called jlocator, which will use JQuery under the hood. But from user perspective, jlocator looks very much the same as clocator with a set of attributes that define the search criteria and some extra features.
As you said, your second propose is better and it is what I expect. Don't worry about the return elements. For some methods, the JQuery selector should return multiple elements, but for some other methods, it should return a single element. For instance, when you click on a UI element. If for some reason, the JQuery returns multiple element in such a case, it usually means something is wrong and the search criteria, i.e., attributes provided by the user is not enough to locate the specific UI element on the UI. The user should refine the jlocator definition. This is actually the same for XPath, right? XPath could also return multiple elements. It is the user's responsibility to define the appropriate jlocator. You will not work alone for the Engine project. We will join you later since we are working on the TrUMP project now. You just need to spend more time to look at Selenium-Core and do some prototype for us. 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 -~----------~----~----~----~------~----~------~--~---
