Open Bug 1838269 Opened 11 months ago Updated 10 months ago

Make "session.end" command work for the session which was created with Webdriver classic and then upgraded to bidi

Categories

(Remote Protocol :: WebDriver BiDi, task, P3)

task

Tracking

(Not tracked)

People

(Reporter: Sasha, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

In the scope of bug 1829337 we covered only the case of ending bidi only session.
The problem was that geckodriver keeps the state of the session and doesn't know that we removed the session, so when we would try to create a new session it would throw an error Session is already started.
At the time, there were two ideas of how we could solve it:

  • on the geckodriver always allow sending command to create a new session, if it succeeds assume the session was removed outside and update the local state;
  • if we decide to use geckodriver as a proxy at least for the cases of classic and bidi, we could update the internal state on "session.end" command.
Blocks: 1829336
Depends on: 1829337
Priority: -- → P3
Depends on: 1839183
You need to log in before you can comment on or make changes to this bug.