wire protocol documentation issues

[lukeis]

Originally reported on Google Code with ID 3551

Selenium version: 2.20 (Java server)
OS: Debian Wheezy (testing)
Browser: Firefox
Browser version: default 2.20 version

Below are some features of the Java server implementation that are undocumented in
the specification, and should likely be added there or included in a documentation
page specific to the Java server. I discovered these problems while implementing a
client library in Haskell. Because I haven't tested my client with other servers yet,
I do not know if these are only quirks of the Java implementation or quirks that can
be found in other servers.

(1) browser-specific capabilities are undocumented in the wire spec but listed here:
https://code.google.com/p/selenium/wiki/DesiredCapabilities

(2) JSON errors codes above 32 are undocumented in the wire protocol spec. This includes
34, 51, and 52. I found these error codes in the Python client source.

(3) JSON fields which are documented to be strings will be set to null instead of an
empty string. They should either be documented as string|null, or set to always be
strings

Reported by adamadamadamamiadam on 2012-03-13 20:56:10

[lukeis]

(1) DesiredCapabilities is the source for all capabilities documentation now, the JsonWireProtocol
just doesn't link to it yet. If we were putting them in JsonWireProtocol, the browser-specific
capabilities still wouldn't be listed because they are not common fields (which is
one of the reasons the DesiredCapabilities page was started).

(2) Yes, these need to be documented.

(3) Examples please.

Reported by jmleyba on 2012-03-13 22:45:35

• Status changed: Accepted
• Labels added: Component-Docs

[lukeis]

Reported by luke.semerau on 2015-09-17 17:44:48

• Labels added: Restrict-AddIssueComment-Commit