Inconsistency with script timeouts

There is an inconsistency in the spec with defining what timeouts are for a session and defining how timeouts are set.

From timeout definition:

A session has an associated session script timeout that specifies a time to wait for scripts to run. If equal to null then session script timeout will be indefinite. Unless stated otherwise it is 30,000 milliseconds.

From the steps to deserialize as a timeout

If value is not an integer, or it is less than 0 or greater than 2⁶⁴ – 1, return error with error code invalid argument.

So a session may have its session script timeout set to null for an indefinite timeout, but the set timeouts command is defined to reject null as a parameter. This makes it impossible to configure an indefinite script timeout.

Read webdriver-spec.html at the session script timeout definition and the “deserialize as a timeout” steps linked in the issue. Check how the set timeouts command passes its script timeout value; done means the specification consistently documents whether null can configure an indefinite script timeout.