Capybara Element returned by Find method is taking a wrong coordinate

By -

I have running a System Test with Ruby On Rails and Minitest, but an error is shown.

Error: enter image description here

edit: please copy and paste anything from a terminal rather than posting pictures ->

Error:
RequestsTest#test_Admin_User_should_create_request:
Selenium: :WebDriver: :Error: :ElementClickInterceptedError: 
  element click intercepted: Element <a id="request__tags-list" href="#" 
class="input-tag-items" dat a-action="click->input-tag box#itemsClick">...</a> is not clickable at point (686, 23). 
Other element would receive the click: <header class="request-panel-header" data-controller="request">…</header>
(Session info: chrome=120.0.6099.130)
test/system/requests_test.rb:480:in execute_test_new_request' 
test/system/requests_test.rb:54:in block in <class:RequestsTest>'

HTML:

<a id="request__tags-list" href="#" class="input-tag-items" data-action="click->input-tag-box#itemsClick"></a>

My Test:

tags_list = find("#request__tags-list")
puts tags_list.rect
tags_list.click  # click on link

I tried using click_link method but it didn't work either. The same error is shown.

I noticed that "tags_list.rect" prints coordinates that do not correspond to the tags_list coordinates.

#<struct Selenium::WebDriver::Rectangle x=316.6037902832031, y=31.733491897583008, width=739, height=20>

when in reality, the Y coordinate is much further down the page, 480 approximately.

Some idea what is happening.

Thanks!

SO: Windows 11

Ruby Version: ruby 3.2.2 (2023-03-30 revision e51014f9c0) [x64-mingw-ucrt]

Rails Version: Rails 7.0.8



Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more