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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow for longer Ajax wait period #724

Closed
adderthorn opened this issue Jun 19, 2019 · 3 comments
Closed

Allow for longer Ajax wait period #724

adderthorn opened this issue Jun 19, 2019 · 3 comments

Comments

@adderthorn
Copy link

馃殌 Feature Proposal

To allow the ability to specify a longer Ajax wait period than the default of 30000ms.

Motivation

I am working to automate an Ajax-heavy application using selenium IDE. This application has Ajax calls that can take longer than 30 seconds, but the browser extension-based selenium IDE version does not seem to have a way to wait longer than 30000ms for these requests.

I am having a hard time working around getting the following errors on my steps:

waitForElementPresent on xpath=//some/xpath/value Failed: Ajax Wait timed out after 30000ms

Example

If I could specify a longer timeout period (e.g. 120000ms) I would be able to use selenium IDE, but as it stands I am not sure I can workaround this issue.

@98gmarquee
Copy link

98gmarquee commented Jun 19, 2019

Are you using the old ide or the newer one that works with chrome/firefox quantum (v57+)?

The old one let you define the wait time in Options->Options...:
2019-0619-SelIDE2 9 1-WaitTimeSetting

The new one requires that you put a wait time in Value field for each command that is a "wait":
2019-0619-SelIDE3 9 0-WaitTimeUsage

Or I'm misunderstanding your problem and you can ignore my comment entirely. :)

@adderthorn
Copy link
Author

I am using the new web extension version for FF quantum+. I did use the wait for element visible, but it still seems to ajax timeout regardless of the value. Maybe it's a bug rather than a feature?

image

@tourdedave
Copy link
Contributor

This looks like a bug. Please open a bug report and follow the issue template.

@lock lock bot locked and limited conversation to collaborators Aug 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants