While implementing the queuing mechanism for Actions in our WebDriver BiDi code base for Firefox I noticed that for the Release Actions command we are just trying to run tick actions, but do not queue this up as a task. That means running a Release Actions command in parallel to the Perform Actions command in BiDi will immediately trigger the release of inputs which in most cases will be a no-op and later on will not reset the inputs unless the browsing context (navigable) gets closed or Release Actions is called again.

I'm going to add a wdspec test for both commands as part of my work on https://bugzilla.mozilla.org/show_bug.cgi?id=1915798.