Dominic, I just realized that you were asking for the case of multiple DslContext classes. There are two parts, on each DslContext class, you need to set the flag to make Tellurium Core to generate the jQuery cache meta commands. On the Engine side, i.e., Selenium core, there is a flag to turn on/off the caching mechanism. Thus, it is global in this sense.
In Tellurium 0.7.0 and Engine 0.1.0, this inconsistency will be removed because the caching will be handled by another tier, i.e., the bundle processor, and the DslContext class does not need to generate meta commands any more. Thus, the jquerycache locate strategy will be removed. But there is still a flag in DslContext for you to turn on/off the caching, which should be global for multiple DslContext classes. Thanks, Jian On Wed, Jun 10, 2009 at 8:21 AM, dominicm <[email protected]>wrote: > > Hi, > > Just converting the last of my tests to use jQuery and have found that > jquery cannot fine IDs with a ".", e.g. "dateOfBirth.month". XPath has > no problem with IDs of this type and if I use name instead it works. > > Also, what is the best way to enable the jQuery selector cache? Should > I just run enableSelectorCache for each UI module, or is it a global > setting? > > Thanks > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
