Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handling alerts sometimes fails with Chrome #652

Closed
aaltat opened this issue Sep 5, 2016 · 2 comments
Closed

Handling alerts sometimes fails with Chrome #652

aaltat opened this issue Sep 5, 2016 · 2 comments

Comments

@aaltat
Copy link
Contributor

aaltat commented Sep 5, 2016

With Chrome 53.0.2785.92, chromedriver 2.23.409687 and selenium 2.53.6 the alert acceptance test seems be failing, again.

There seems to be timing issue with chrome which causes WebDriverException: Message: unknown error: unhandled inspector error on random but frequent places. Fix the error or at least perform few times a re-try.

@aaltat aaltat added the bug label Sep 5, 2016
@aaltat aaltat added this to the v2.0 milestone Sep 5, 2016
@aaltat aaltat self-assigned this Sep 5, 2016
@aaltat aaltat mentioned this issue Sep 9, 2016
5 tasks
@aaltat aaltat closed this as completed in dcc7ff9 Sep 16, 2016
Gaurang033 pushed a commit to Gaurang033/Selenium2Library that referenced this issue Oct 17, 2016
* Improves alert hadling for Chrome (robotframework#652)

In Chrome is often a random WebDriverException which caused
by unknow reson. This commit creates a retry functionality
that improves alert handling for Crome.

Fixes robotframework#652

* Refactored the code to simplify the logic

* Changed class attribute to better describe what it does

* Updates alert handling based on the comment review

* Changed class atributes names to describe better what they do

* Fixed based on the comments
VitoAlbano pushed a commit to VitoAlbano/Selenium2Library that referenced this issue Oct 18, 2016
* Improves alert hadling for Chrome (robotframework#652)

In Chrome is often a random WebDriverException which caused
by unknow reson. This commit creates a retry functionality
that improves alert handling for Crome.

Fixes robotframework#652

* Refactored the code to simplify the logic

* Changed class attribute to better describe what it does

* Updates alert handling based on the comment review

* Changed class atributes names to describe better what they do

* Fixed based on the comments
@pekkaklarck pekkaklarck changed the title Fix alerts for chrome Handling alerts sometimes fails with Chrome Sep 26, 2017
@lionlamb
Copy link

I am still encountering this issue in Chrome but not Firefox.
I am using the latest SeleniumLibrary, curious if there is workaround on it? I pasted the error below:


Login To Page                                                  [7092:19556:0716/174928.983:ERROR:install_util.cc(597)] Unable to read registry value HKLM\SOFTWARE\Policies\Google\Chrome\MachineLevelUserCloudPolicyEnrollmentToken for writing result=2

DevTools listening on ws://127.0.0.1:57742/devtools/browser/e862df1c-13e1-464f-b426-6b650734699a
[ WARN ] Keyword 'Capture Page Screenshot' could not be run on failure: UnexpectedAlertPresentException: Alert Text: None
Message: unexpected alert open: {Alert text : This is demo pop up.}
  (Session info: chrome=67.0.3396.99)
  (Driver info: chromedriver=2.40.565498 (ea082db3280dd6843ebfb08a625e3eb905c4f5ab),platform=Windows NT 10.0.16299 x86_64)

@aaltat
Copy link
Contributor Author

aaltat commented Jul 16, 2018

I am pretty that your problem is not same as this because it's over two years old. If you think that there is a problem in the library, please open new issue. If you are seeking support, please see https://github.com/robotframework/SeleniumLibrary/blob/master/README.rst#support

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants