During my recent editing of the spec I noticed the same issue.
It appears that it was clearly defined that an invalid "mode" parameter
should throw a TypeError, but no behaviour was defined for invalid
"direction" parameters.
I fixed this by specifying that invalid "direction" parameters should a
We need to define in the spec what should happen if a developers defines an
invalid "mode" or "direction". Do we throw a TypeError Exception or revert to
defauls?
FF seems to allow this behavior and reverts back to a readOnly transaction mode
and a direction of next, respectively:
* db.transac
