Changing the DOM wait timings

Applying eValid to AJAX applications that require advanced DOM-based methods.

Changing the DOM wait timings

Postby LoganRam » Thu Apr 18, 2019 12:22 pm

Hi

What's the story on this one?

I want to change the DOM-based waits to make SURE that the page content has settled down.

What is your recommendation?

Thanks
LoganRam
 
Posts: 1
Joined: Thu Apr 18, 2019 12:17 pm

Re: Changing the DOM wait timings

Postby eValid » Fri Apr 19, 2019 9:27 am

LoganRam wrote:Hi

What's the story on this one?

I want to change the DOM-based waits to make SURE that the page content has settled down.

What is your recommendation?

Thanks


Thanks for asking LoganRam.

There's no problem changing two waits in sequence.

For example:

SyncOnText (a first text fragment)
...do something...
SyncOnText (a second text fragment)

where we are using the command:

http://e-valid.com/Products/Documentati ... .text.html

The first sync will wit until the condition is met; they you release the playback for the "intermediate actions".

Then the second sync starts up.

This is perfectly OK, and is good practice.

However, if you script this:

SyncOnText (a first text fragment)
SyncOnText (a second text fragment)

then the same thing happens.

What is interesting is that if the page is stable after the first sync, and there is nothing going on in the page that is autonomous, then you could just as well write:

SyncOnText (a second text fragment)

The question is, if the "second text fragment" is there does it imply that the "first text fragment" was already found?

That depend on the application, and our general rule is, "sync early and often".

More sync's are better that fewer.


-- eValid Support
eValid
 
Posts: 1961
Joined: Tue Jan 01, 2008 12:48 pm
Location: USA


Return to AJAX Applications & DOM Processing

Design Downloaded from free phpBB templates | free website templates | Free Web Buttons