Please report any other irregularities here.
The spec sayeth: “If command is not ‘new session’: […] If ‘session id’ is not equal to the id of any session in the ‘list of active sessions’, send an error with error code ‘invalid session id’, then jump to step 1 in this overall algorithm.” This means we need to respond with an InvalidSessionIdError whenever we receive a command with a session ID that isn't the current one, unless the command is for a new session.
Whiteboard: [good first bug][lang=js]
I am interested in fixing this bug.
After the Marionette protocol changes to level 3 (bug 1211489) this won’t be necessary any more since we do no longer use the session ID as a token for communicating with Marionette. If you’re still interested in helping, please consider taking on bug 1153828.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.