Forking from  issue 918268 .  For some reason, if an extension message response is delivered with a user gesture before a web page can consume the gesture, the creation of the scoped gesture from the token results in the token being consumed.

This is being forked off to track the underlying cause, since 918268 was fixed by rolling back the native bindings feature unless UAv2 is enabled (the issue isn't present with UAv2).