New issue
Advanced search Search tips

Issue 665444 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

After login redirection immediately back to login page with error "Expected condition failed: waiting for visibility of Proxy element for: DefaultElementLocator 'By.xpath: //*[@id='pt1:pgl3']/tbody/tr/td[2]/span' (tried for 20 second(s) with 500 MILLISECONDS interval)"

Reported by amol.gai...@gmail.com, Nov 15 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0

Steps to reproduce the problem:
1. Configuration: Windows 10, Selenium 3.0.1, Chrome 54.0.2840.99 m (64-bit), ChromeDriverwin32
2. Accessed the Application Login page
3. Entered valid login credentials and submitted
4. Redirection to internal home page and within a second its throwing back to the Login page
Note: Same script works fine on IE, FF, Safari. ONLY on Chrome the selenium sync is not consistent. Finding of the element is before the page is even getting loaded.
Have used Thread.sleep, waitforPagetoLoad, waitforelementvisible logic but nothing works

What is the expected behavior?
After valid login, redirection to the applications internal Home page should happen

What went wrong?
It is getting thrown back to the login page with error as "Expected condition failed: waiting for visibility of Proxy element for: DefaultElementLocator 'By.xpath: //*[@id='pt1:pgl3']/tbody/tr/td[2]/span' (tried for 20 second(s) with 500 MILLISECONDS interval)"

Did this work before? N/A 

Chrome version: 54.0.2840.99 m (64-bit)  Channel: stable
OS Version: 10.0
Flash Version:
 
Components: Internals>Logging
Labels: TE-NeedsTriageHelp
Adding label TE-NeedsTriageHelp for further investigation.

Thanks...!!
Components: Tests>WebDriver
amol.gaikwad4u@, Does this issue happen manually or it is only when executed through chromedriver? Can you please share a repro test code along with the test page?  What version of Chromedriver are you using? You can find the version by running "chromedriver.exe --v" in command prompt.
Labels: M-57
Status: WontFix (was: Unconfirmed)
Since there is no response from the issue reporter, closing the issue.

Sign in to add a comment