It is fine not to post the UI module and I understand company policies. But it would be great if you could have some html snippet created by your own or from a sample page that can reproduce the problem. Usually, it is very difficult to diagnose the problem without looking at the actual code example.
I guess the red border appeared because the "mouseOver" or "focus" event (do you have event handlers for them?) triggered the validation, but for some reason, the key event did not get handled properly and thus the characters were not typed in. On Mon, Oct 4, 2010 at 11:02 AM, Rudy Bonefas <[email protected]> wrote: > The 'type' command works fine, and I'm able to validate the location. > I do have key handlers attached to the textarea; we have a max char > limit on the field and as the user > types we have a label that displays how many allowed characters > remain. My UI module code is pretty large I don't > think my company would want me to post it. I'm using the ExtJS 3.2.0 > toolkit. What I can do is write a UIModule to > work against one of the public ExtJS sample pages that includes a UI > module and then send it to you. > > An interesting side note: With the ExtJS form field validation on, > the field value is initially undefined. When the user clicks or tabs > onto the field > the validator runs and Ext outlines the empty field with a red border > indicating the field value is currently invalid. When I run my > UIModule, the field is actually > invalidated (the red border appears) but none of the text characters > get added to the field. > > On Oct 1, 4:52 pm, Jian Fang <[email protected]> wrote: > > Did the "type" command work for you? keyType actually consists of a > series > > of key events such as keyUp and keyDown. Or do you have some JavaScript > > event handlers attached to the textarea? Could you post your UI module > > definition and the html snippet for textarea? To rule out the locating > > problem, it is always good to call > > > > diagnose(uid) > > > > on the problematic UI to make sure the textarea can be found correctly. > > > > Have you tried pure Selenium to see if it works? For instance, use > Selenium > > IDE? > > > > Thanks, > > > > Jian > > > > > > > > On Fri, Oct 1, 2010 at 4:30 PM, Rudy Bonefas <[email protected]> wrote: > > > I tried useTelluriumAPI(false) in my DSLContext, didn't work. > > > I tried useTelluriumEngine(false) in my test setup, did'nt work. > > > and I tried useCssSelector(false) in my test setup, didn't work. > > > > > For further clarification, I'm trying to keytype into a textarea > > > element as opposed to an inputbox. > > > > > On Oct 1, 9:30 am, Jian Fang <[email protected]> wrote: > > > > Are you using the Selenium Wrapper mode, i.e., called > > > > useTelluriumEngine(false)? If not, please try that. > > > > > > You can try to switch between XPath and CSS selector with the > command: > > > > > > useCssSelector(boolean isUse) > > > > > > to see if it works. IE is difficult to test because it builds the DOM > > > > differently. The Selenium Wrapper mode > > > > actually calls Selenium APIs and hope it works for you. > > > > > > I will add the controlKeyDown method to 0.8.0 snapshot soon to see if > > > that > > > > helps. > > > > > > Thanks, > > > > > > Jian > > > > > > On Thu, Sep 30, 2010 at 5:38 PM, Rudy Bonefas <[email protected]> > > > wrote: > > > > > From searching the discussion board, I noticed that others are > having > > > > > problems with the keyType event not being processed by IE. > > > > > > > Is there a fix or workaround for this? > > > > > > > Also, using ctrl-key via > > > > > > > customDirectCall 'controlKeyDown', null > > > > > > > does not work in IE either. > > > > > > > I'm running IE7 with the Sept 5th 0.8.0 build of tellurium core. > > > > > > > -- > > > > > 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]<tellurium-users%[email protected]> > <tellurium-users%2Bunsubscribe@ googlegroups.com> > > > <tellurium-users%2Bunsubscribe@ googlegroups.com> > > > > > . > > > > > For more options, visit this group at > > > > >http://groups.google.com/group/tellurium-users?hl=en. > > > > > -- > > > 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]<tellurium-users%[email protected]> > <tellurium-users%2Bunsubscribe@ googlegroups.com> > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/tellurium-users?hl=en. > > -- > 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]<tellurium-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/tellurium-users?hl=en. > > -- 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.
