Skip to content
This repository has been archived by the owner on Nov 29, 2018. It is now read-only.

WebDriverTimeoutException in AsyncJavaScriptExecutor returns Milliseconds instead of TotalMilliseconds #8417

Open
lukeis opened this issue Mar 4, 2016 · 2 comments
Open

WebDriverTimeoutException in AsyncJavaScriptExecutor returns Milliseconds instead of TotalMilliseconds #8417

lukeis opened this issue Mar 4, 2016 · 2 comments
Assignees
@lukeis
Labels
Lang-CSharp Priority-Medium Restrict-AddIssueComment-Commit Status-New Status-Untriaged Type-Defect

Comments

@lukeis
Copy link
Member

lukeis commented Mar 4, 2016

Originally reported on Google Code with ID 8417

https://code.google.com/p/selenium/source/browse/dotnet/src/webdriver/Internal/AsyncJavaScriptExecutor.cs?spec=svn7da094f39f9b6d52ea47d3d37e0ab28bd01f01d4&r=7da094f39f9b6d52ea47d3d37e0ab28bd01f01d4#142

The WebDriverTimeoutException returns Milliseconds instead of TotalMilliseconds.  This
makes the error returned seem incorrect as it excludes milliseconds greater than 1
second.

This should probably use a System.Stopwatch rather than a DateTime.

Reported by [email protected] on 2015-01-21 18:09:30
@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016

Reported by barancev on 2015-03-08 21:08:20

  • Labels added: Lang-CSharp

@lukeis lukeis self-assigned this Mar 4, 2016
@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016

Reported by luke.semerau on 2015-09-17 17:47:30

  • Labels added: Restrict-AddIssueComment-Commit

@SeleniumHQ SeleniumHQ locked and limited conversation to collaborators Mar 4, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@lukeis lukeis

Labels
Lang-CSharp Priority-Medium Restrict-AddIssueComment-Commit Status-New Status-Untriaged Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lukeis