04-07-2017, 04:18 AM
I am having issues running scripts in Chrome and it seems to be related to (a) the target being a Single Page App and (b) the navigate command not detecting the end condition. The same script runs fine in Firefox!
Also: I have a private instance of WPT that runs through a batch of URLs/Scripts every 2 hours and I found that tests targeting Single Page Apps started showing this behavior on or around the beginning of March ... I proceeded to run one of these scripts on public WPT and got the same issue:
Firefox working: http://www.webpagetest.org/result/170404...e1ebaa2c6/
Chrome failing: http://www.webpagetest.org/result/170404...bc67d1a99/
Script:
The Chrome screenshots are still showing the sso.godaddy.com page (from the initial navigate statement) while the Firefox screenshots are showing the desired target page.
Agents are currently on version 371
If anybody is seeing this behavior or wants to troubleshoot this, hit me up!
Also: I have a private instance of WPT that runs through a batch of URLs/Scripts every 2 hours and I found that tests targeting Single Page Apps started showing this behavior on or around the beginning of March ... I proceeded to run one of these scripts on public WPT and got the same issue:
Firefox working: http://www.webpagetest.org/result/170404...e1ebaa2c6/
Chrome failing: http://www.webpagetest.org/result/170404...bc67d1a99/
Script:
Code:
logData 0
navigate https://sso.godaddy.com
setValue id=username <username>
setValue id=password <password>
clickAndWait id=submitBtn
logData 1
navigate https://dcc.godaddy.com/domains
The Chrome screenshots are still showing the sso.godaddy.com page (from the initial navigate statement) while the Firefox screenshots are showing the desired target page.
Agents are currently on version 371
If anybody is seeing this behavior or wants to troubleshoot this, hit me up!