I also realized that I was very much lacking data in my report, and for
that I apologize:
Ruby Version: ruby 2.3.3p222 (2016-11-21 revision 56859) [i386-mingw32]
Watir Version: 6.11.0
Browser: Chrome Version 67.0.3396.87 (Official Build) (64-bit)
Chromedriver Version: 2.40.565498
OS: Windows 8.1 Pro
On Wednesday, June 20, 2018 at 9:14:25 PM UTC-4, Steve Parrado wrote:
>
> I recreated it by navigating to a public facing website, identifying an
> element at the top of the page, and then scrolling down and performing the
> click and click+control. Here is the output:
>
> irb(main):009:0> @browser.goto("http://www.newhomeguide.com";)
> => "http://www.newhomeguide.com";
> irb(main):010:0> @browser.send_keys :end
> => nil
> irb(main):011:0> Selenium::WebDriver.logger.level = :info
> => :info
> irb(main):012:0> @browser.element(:class, 'searchSubmit').click
> 2018-06-20 21:08:49 INFO Selenium -> POST
> session/347b09a05ad4e6ffe8661cb3a0b0a9af/element
> 2018-06-20 21:08:49 INFO Selenium >>>
> http://127.0.0.1:9515/session/347b09a05ad4e6ffe8661cb3a0b0a9af/element |
> {"using":"xpath","value":".//*[contains(concat(' ', @class, ' '), '
> searchSubmit ')]"}
>
> 2018-06-20 21:08:49 INFO Selenium <-
> {"sessionId":"347b09a05ad4e6ffe8661cb3a0b0a9af","status":0,"value":{"ELEMENT":"0.4022756665195595-2"}}
> 2018-06-20 21:08:49 INFO Selenium -> POST
> session/347b09a05ad4e6ffe8661cb3a0b0a9af/element/0.4022756665195595-2/click
> 2018-06-20 21:08:50 INFO Selenium <-
> {"sessionId":"347b09a05ad4e6ffe8661cb3a0b0a9af","status":13,"value":{"message":"unknown
>
> error: Element \u003Cinput type=\"submit\" value=\"SEARCH\" class=\"searchS
> ubmit\"> is not clickable at point (1040, 25). Other element would receive
> the click: \u003Ca
> href=\"https://newhomeguide.com/category/all\";>...\u003C/a>\n
> (Session info: chrome=67.0.3396.87)\n (Dri
> ver info: chromedriver=2.40.565498
> (ea082db3280dd6843ebfb08a625e3eb905c4f5ab),platform=Windows NT 6.3.9600
> x86_64)"}}
> Selenium::WebDriver::Error::UnknownError: unknown error: Element <input
> type="submit" value="SEARCH" class="searchSubmit"> is not clickable at
> point (1040, 25). Other element would receive the click:
> <a href="https://newhomeguide.com/category/all";>...</a>
> (Session info: chrome=67.0.3396.87)
> (Driver info: chromedriver=2.40.565498
> (ea082db3280dd6843ebfb08a625e3eb905c4f5ab),platform=Windows NT 6.3.9600
> x86_64)
> from
> C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.4.4/lib/selenium/webdriver/remote/response.rb:69:in
>
> `assert_ok'
> from
> C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.4.4/lib/selenium/webdriver/remote/response.rb:32:in
>
> `initialize'
> from
> C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.4.4/lib/selenium/webdriver/remote/http/common.rb:83:in
>
> `new'
> from
> C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.4.4/lib/selenium/webdriver/remote/http/common.rb:83:in
>
> `create_response'
> from
> C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.4.4/lib/selenium/webdriver/remote/http/default.rb:107:in
>
> `request'
> from
> C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.4.4/lib/selenium/webdriver/remote/http/common.rb:61:in
>
> `call'
> from
> C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.4.4/lib/selenium/webdriver/remote/bridge.rb:170:in
>
> `execute'
> from
> C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.4.4/lib/selenium/webdriver/remote/oss/bridge.rb:579:in
>
> `execute'
> from
> C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.4.4/lib/selenium/webdriver/remote/oss/bridge.rb:328:in
>
> `click_element'
> from
> C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.4.4/lib/selenium/webdriver/common/element.rb:74:in
>
> `click'
> from
> C:/Ruby23/lib/ruby/gems/2.3.0/gems/watir-6.11.0/lib/watir/elements/element.rb:135:in
>
> `block in click'
> from
> C:/Ruby23/lib/ruby/gems/2.3.0/gems/watir-6.11.0/lib/watir/elements/element.rb:650:in
>
> `element_call'
> from
> C:/Ruby23/lib/ruby/gems/2.3.0/gems/watir-6.11.0/lib/watir/elements/element.rb:126:in
>
> `click'
> from (irb):12
> from C:/Ruby23/bin/irb.cmd:19:in `<main>'
> irb(main):013:0> @browser.element(:class, 'searchSubmit').click(:control)
> 2018-06-20 21:09:01 INFO Selenium -> POST
> session/347b09a05ad4e6ffe8661cb3a0b0a9af/element
> 2018-06-20 21:09:01 INFO Selenium >>>
> http://127.0.0.1:9515/session/347b09a05ad4e6ffe8661cb3a0b0a9af/element |
> {"using":"xpath","value":".//*[contains(concat(' ', @class, ' '), '
> searchSubmit ')]"}
>
> 2018-06-20 21:09:01 INFO Selenium <-
> {"sessionId":"347b09a05ad4e6ffe8661cb3a0b0a9af","status":0,"value":{"ELEMENT":"0.4022756665195595-2"}}
> 2018-06-20 21:09:01 INFO Selenium -> POST
> session/347b09a05ad4e6ffe8661cb3a0b0a9af/keys
> 2018-06-20 21:09:01 INFO Selenium >>>
> http://127.0.0.1:9515/session/347b09a05ad4e6ffe8661cb3a0b0a9af/keys |
> {"value":["î?%"]}
> 2018-06-20 21:09:01 INFO Selenium <-
> {"sessionId":"347b09a05ad4e6ffe8661cb3a0b0a9af","status":0,"value":null}
> 2018-06-20 21:09:01 INFO Selenium -> POST
> session/347b09a05ad4e6ffe8661cb3a0b0a9af/moveto
> 2018-06-20 21:09:01 INFO Selenium >>>
> http://127.0.0.1:9515/session/347b09a05ad4e6ffe8661cb3a0b0a9af/moveto |
> {"element":"0.4022756665195595-2"}
> 2018-06-20 21:09:01 INFO Selenium <-
> {"sessionId":"347b09a05ad4e6ffe8661cb3a0b0a9af","status":0,"value":null}
> 2018-06-20 21:09:01 INFO Selenium -> POST
> session/347b09a05ad4e6ffe8661cb3a0b0a9af/click
> 2018-06-20 21:09:01 INFO Selenium >>>
> http://127.0.0.1:9515/session/347b09a05ad4e6ffe8661cb3a0b0a9af/click |
> {"button":0}
> 2018-06-20 21:09:01 INFO Selenium <-
> {"sessionId":"347b09a05ad4e6ffe8661cb3a0b0a9af","status":0,"value":null}
> 2018-06-20 21:09:01 INFO Selenium -> POST
> session/347b09a05ad4e6ffe8661cb3a0b0a9af/keys
> 2018-06-20 21:09:01 INFO Selenium >>>
> http://127.0.0.1:9515/session/347b09a05ad4e6ffe8661cb3a0b0a9af/keys |
> {"value":["î?%"]}
> 2018-06-20 21:09:01 INFO Selenium <-
> {"sessionId":"347b09a05ad4e6ffe8661cb3a0b0a9af","status":0,"value":null}
> => nil
>
>
> What I noticed here is that the ".click(:control)" actually clicked the
> event and behaved as if it were fired click event with the modifier, and it
> opened a new tab.
>
>
> On Thursday, June 14, 2018 at 11:55:07 AM UTC-4, Titus Fortner wrote:
>>
>> This would be a Chromedriver issue, so we'd need to see what commands
>> are getting sent to the driver.
>>
>> Can you run both with `Selenium::WebDriver.logger.level = :info`?
>> Is the html public that we could get them a reproducible issue?
>> On Thu, Jun 14, 2018 at 6:29 AM Steve Parrado <parr...@gmail.com> wrote:
>> >
>> > Has anyone seen similar behavior? I am still at a loss about this.
>> >
>> > On Thursday, June 7, 2018 at 12:00:07 AM UTC-4, Steve Parrado wrote:
>> >>
>> >> I was attempting to write a function that performed a ctrl+click so
>> that if the click caused a page navigation, it would be in a new window
>> which would leave the original window in a particular state. It was during
>> this that I found that when I click an element that is obscured by another
>> object (perhaps due to responsive design issues) I get a message indicating
>> this (as expected)..
>> >>
>> >> @browser.element(:id, "button_login").click
>> >> Selenium::WebDriver::Error::UnknownError: unknown error: Element
>> <button type="submit" id="button_login" class="btn btn-orange
>> btn-block">...
>> >> ent would receive the click: <div class="panel-heading
>> border-light">...</div>
>> >> (Session info: chrome=66.0.3359.181)
>> >> (Driver info: chromedriver=2.38.552522
>> (437e6fbedfa8762dec75e2c5b3ddb86763dc9dcb),platform=Windows NT 6.3.9600
>> x86_64)
>> >> from
>> C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.4.4/lib/selenium/webdriver/remote/response.rb:69:in
>>
>> `assert_ok'
>> >> from
>> C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.4.4/lib/selenium/webdriver/remote/response.rb:32:in
>>
>> `initialize'
>> >> from
>> C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.4.4/lib/selenium/webdriver/remote/http/common.rb:83:in
>>
>> `new'
>> >> from
>> C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.4.4/lib/selenium/webdriver/remote/http/common.rb:83:in
>>
>> `create_response'
>> >> from
>> C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.4.4/lib/selenium/webdriver/remote/http/default.rb:107:in
>>
>> `request'
>> >> from
>> C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.4.4/lib/selenium/webdriver/remote/http/common.rb:61:in
>>
>> `call'
>> >> from
>> C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.4.4/lib/selenium/webdriver/remote/bridge.rb:170:in
>>
>> `execute'
>> >> from
>> C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.4.4/lib/selenium/webdriver/remote/oss/bridge.rb:579:in
>>
>> `execute'
>> >> from
>> C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.4.4/lib/selenium/webdriver/remote/oss/bridge.rb:328:in
>>
>> `click_element'
>> >> from
>> C:/Ruby23/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.4.4/lib/selenium/webdriver/common/element.rb:74:in
>>
>> `click'
>> >> from
>> C:/Ruby23/lib/ruby/gems/2.3.0/gems/watir-6.11.0/lib/watir/elements/element.rb:135:in
>>
>> `block in click'
>> >> from
>> C:/Ruby23/lib/ruby/gems/2.3.0/gems/watir-6.11.0/lib/watir/elements/element.rb:650:in
>>
>> `element_call'
>> >> from
>> C:/Ruby23/lib/ruby/gems/2.3.0/gems/watir-6.11.0/lib/watir/elements/element.rb:126:in
>>
>> `click'
>> >> from (irb):1
>> >> from C:/Ruby23/bin/irb.cmd:19:in `<main>'
>> >>
>> >>
>> >>
>> >> However, when I perform a modified click on the same element (in this
>> case with :control) I get no error message.
>> >>
>> >> @browser.element(:id, "button_login").click(:control)
>> >> => nil
>> >>
>> >>
>> >> It seems to me that the error from the unmodified click should be
>> present in the modified click as the object being interacted with has not
>> changed, just the interaction on the object itself has.
>> >
>> > --
>> > --
>> > Before posting, please read
>> https://github.com/watir/watir_meta/wiki/Guidelines-for-Posting-to-Watir-General-Google-Group.
>>
>>
>> > In short: search before you ask, be nice.
>> >
>> > watir-...@googlegroups.com
>> > http://groups.google.com/group/watir-general
>> > watir-genera...@googlegroups.com
>> > ---
>> > 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 watir-genera...@googlegroups.com.
>> > For more options, visit https://groups.google.com/d/optout.
>>
>
--
--
Before posting, please read
https://github.com/watir/watir_meta/wiki/Guidelines-for-Posting-to-Watir-General-Google-Group.
In short: search before you ask, be nice.
watir-general@googlegroups.com
http://groups.google.com/group/watir-general
watir-general+unsubscr...@googlegroups.com
---
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 watir-general+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
