Something in the DOM is requiring an interaction that your test isn't accounting for. Without a reproducible test case to look at, I can't help you any more.
On Sat, Dec 17, 2016 at 3:02 PM, Raja gopalan <[email protected]> wrote: > Yes, I have tried with watir-scroll as well, but it also throws the error. > > > On Sunday, December 18, 2016 at 2:30:31 AM UTC+5:30, Titus Fortner wrote: >> >> Selenium "displayed" property is about what is in the DOM, not what is in >> the viewport. Taking an action on an element is supposed to move it into >> the viewport first by default. If it isn't doing that for some reason (it >> is rare but it happens), use watir-scroll https://github.com/p0deje/wati >> r-scroll >> >> You can scroll the element into the viewport and then take actions on it >> without needing to set a debug point. >> >> Titus >> >> On Saturday, December 17, 2016 at 2:44:24 PM UTC-6, Raja gopalan wrote: >>> >>> Yes, I know classic is only for IE, But when I used watir-webdriverfor >>> both IE and Chrome, both are throwing this same error. It's a lengthy page, >>> that text field is in the deep down of that page(So it's not visible). If I >>> put a debug pointer and stop the program, and then I manually move that >>> text box up to the visibility and then If I press the F8 in RubyMine, it >>> works, but not automatically. But according to the condition, it >>> automatically bring that text_field into visibility,right, but it's not >>> happening. >>> >>> On Sunday, December 18, 2016 at 2:01:44 AM UTC+5:30, Titus Fortner wrote: >>>> >>>> Firstly, watir-classic is Internet Explorer only, and there are a >>>> number of behaviors that will be different between that browser and Google >>>> Chrome. >>>> >>>> Secondly, Selenium and Watir attempt to only allow interactions that >>>> are accessible to a user. Without having a reproducible test case it would >>>> be difficult to diagnose further, but you are likely trying to do something >>>> differently than how a user to the site would be doing it. >>>> >>>> Titus >>>> >>>> On Saturday, December 17, 2016 at 1:57:36 AM UTC-6, Raja gopalan wrote: >>>>> >>>>> I am running the same code in Watir-classic and WATIR 6.0.2 >>>>> >>>>> WATIR-CLASSIC runs without any problem, but WATIR 6.0.2 throwing this >>>>> error >>>>> >>>>>> >>>>>> [12:39:18] [ERROR] : invalid element state: Element is not currently >>>>>> interactable and may not be manipulated >>>>>> (Session info: chrome=55.0.2883.87) >>>>>> (Driver info: chromedriver=2.26.436362 >>>>>> (5476ec6bf7ccbada1734a0cdec7d570bb042aa30),platform=Windows NT >>>>>> 6.1.7601 SP1 x86_64) >>>>>> from C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.0.3/ >>>>>> lib/selenium/webdriver/remote/response.rb:69:in `assert_ok' >>>>>> from C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.0.3/ >>>>>> lib/selenium/webdriver/remote/response.rb:32:in `initialize' >>>>>> from C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.0.3/ >>>>>> lib/selenium/webdriver/remote/http/common.rb:81:in `new' >>>>> >>>>> >>>>> Can anybody suggest me why? >>>>> >>>> -- > -- > Before posting, please read http://watir.com/support. In short: search > before you ask, be nice. > > [email protected] > http://groups.google.com/group/watir-general > [email protected] > > --- > You received this message because you are subscribed to the Google Groups > "Watir General" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. [email protected] http://groups.google.com/group/watir-general [email protected] --- You received this message because you are subscribed to the Google Groups "Watir General" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
