A somewhat common problem in WebDriver is that the test is stuck waiting for a
resource to load, but a user is not sure what could be causing it. We could
keep track of requests via the Network domain. Not sure the best way to get
this information to the user, probably the logging API.
Original issue reported on code.google.com by kkania@chromium.org on 25 Jan 2013 at 12:09
Original issue reported on code.google.com by
kkania@chromium.org
on 25 Jan 2013 at 12:09