Navigation Menu

Skip to content
This repository has been archived by the owner on Nov 29, 2018. It is now read-only.

Selenium 2.33 doesn't "see" visible text though 2.32.1 does see #5717

Open
lukeis opened this issue Mar 4, 2016 · 13 comments
Open

Selenium 2.33 doesn't "see" visible text though 2.32.1 does see #5717

lukeis opened this issue Mar 4, 2016 · 13 comments

Comments

@lukeis
Copy link
Member

lukeis commented Mar 4, 2016

Originally reported on Google Code with ID 5717

Here is a code:

require 'selenium-webdriver'
driver = Selenium::WebDriver.for :firefox
driver.navigate.to 'http://beta.robocast.com/roboshows/new'
driver.find_element(:id, 'url').send_keys 'sdasdasdasd wqewqeqweqwewqqwe'
driver.find_element(:css, '.add_urls_button').click
sleep 2
driver.find_element(:id, 'save_button').click
puts driver.find_element(:id, 'broken_urls_popup_on_save').displayed?
puts driver.find_element(:id, 'broken_urls_popup_on_save').text
driver.quit

When invoked in Selenium 2.32.1 it outputs:
true
Some of your URLs appear to be broken, malware or might have adult content, please
review. Save Review

When invoked in Selenium 2.33 it outputs:
true


As you Selenium 2.33 doesn't see text that is clearly visible in the browser

Reported by botalov.andrey on 2013-05-31 11:10:46

@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016

Could you try this with a different driver? I'm having a similar issue, but only in
firefox - chromedriver sees the element as do humans.

Reported by christoph.neuroth@lusini.com on 2013-06-05 07:42:36

@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016

Reproduced. It fails in 2.32 Java binding too (2.31 works well).

There were changes in 2.32 related to better visibility determination in the case of
an element enclosed in an overflow block.

Unfortunately this new implementation does not take into account elements with "position:fixed"
style that fall out of the regural page flow.

Unfortunately (again) we found another bug related to calculation of coordinates for
elements with "position:fixed" style, a new test added by revision 56e3bae46efd, Firefox
fails this test.

Reported by barancev on 2013-06-05 08:00:19

  • Status changed: Accepted
  • Labels added: Browser-Firefox

@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016

I've added a couple stack overflow questions regarding this issue a couple days back:
http://stackoverflow.com/questions/17602334/element-is-not-currently-visible-and-so-may-not-be-interacted-with-but-another
http://stackoverflow.com/questions/17624312/why-does-the-selenium-firefox-driver-consider-my-modal-not-displayed-when-the-pa

Reported by tonyeung85 on 2013-07-16 14:10:37

@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016

Any update on this issue?

Reported by pavithra.krishna@teamaol.com on 2013-07-17 11:54:59

@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016

It seems like there are a large number of dupes or problems with the same underlying
cause:
Problems: 5703 5713  5745 5747 5765 5773 

Reported by erroneousbee on 2013-07-22 12:55:59

@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016

Hi!

Selenium 2.35 with changes in visibility atom was released.
Could you recheck does this issue still reproduced?

Reported by a.u.savchuk on 2013-08-13 19:00:04

  • Status changed: NeedsClarification

@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016

CSS has been changed at site I provided POC for so I can't reproduce it in neither 2.33.0
nor in 2.34.0

Gem selenium-webdriver 2.35.0 hasn't been released yet.

Reported by botalov.andrey on 2013-08-13 19:24:05

@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016

Hi!

Is this issue still actual for latest Selenium for someone?

Reported by a.u.savchuk on 2013-09-05 16:38:49

@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016

We're seeing this issue with the Firefox driver as of version 2.31, and we have confirmed
that it occurs in 2.35 as well.  

Behavior: He have a table (<td>) consisting of eight rows (<div>), and when you call
findElement(), Selenium can locate all of them, calling getText() on each of those
elements results in the first five rows' content being returned, and empty-String return
value for the last three.  

If you scroll to the right at runtime, Selenium will find the text of the other three
elements (the table is vertical - really a label), but otherwise, it doesn't find any
content.  It's not that the elements aren't available - the findElement returns successfully
for all of them, but somehow Selenium can't find the text unless you scroll forward.

When we roll back to an earlier Firefox driver (e.g. 2.18), the problem goes away,
but with 2.31 and higher, we're seeing this issue.

Any help/fix would be welcome.

Thank you!  :)

Reported by dmclellan on 2013-10-03 18:21:45

@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016

@dmclellan: I hope you know what to do to help us fix it -- provide a sample page to
reproduce the issue instead of a narrative description. FYI: if an element is hidden
behind a border of an overflow:hidden block it is hidden and the text is empty, it
is expected behavior.

Reported by barancev on 2013-10-05 16:29:26

@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016

Was the overflow:hidden a designed change in version 2.3x.0? The overflow:hidden is
dependent on browser size, resolution, font size etc so is a little frustrating if
this is now expected. There's no easy workaround either.

Reported by bekkiandkeith on 2014-06-06 07:54:33

@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016

The original issue is related to wrong coordinates of elements with position:fixed and
is *not* related to visibility:hidden.

If you think there is another issue please fill it and provide a sample scenario and
a sample page to reproduce it.

Reported by barancev on 2014-06-06 08:14:33

  • Status changed: Accepted

@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016

Reported by luke.semerau on 2015-09-17 17:45:12

  • Labels added: Restrict-AddIssueComment-Commit

@SeleniumHQ SeleniumHQ locked and limited conversation to collaborators Mar 4, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant