Fixing .NET responses where value should legitimately be null

SeleniumHQ · Oct 14, 2015 · b0e2f0d · b0e2f0d
1 parent b843bc9
commit b0e2f0d
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/dotnet/src/webdriver/Remote/Response.cs b/dotnet/src/webdriver/Remote/Response.cs
@@ -68,9 +68,9 @@ private Response(Dictionary<string, object> rawResponse, int protocolSpecLevel)
 
             if (protocolSpecLevel > 0)
             {
-                // If the returned object does *not* have a "value" property,
-                // then the responseValue member of the response will be null.
-                if (this.responseValue == null)
+                // If the returned object does *not* have a "value" property
+                // the response value should be the entirety of the response.
+                if (!rawResponse.ContainsKey("value") && this.responseValue == null)
                 {
                     this.responseValue = rawResponse;
                 }