This was added a long time ago to allow async xhr requests to launch
app links. Later on, User Activation V2 made transient user activation
available to any sync/async "user API" in the LocalFrame (Window),
making xhr-request specific state propagation unnecessary.
Note that integration tests for this exist in UrlOverridingTest.
However, this deletion isn't entirely without risk - the Gesture
Carryover timeout was 10 seconds, while the transient activation
timeout is 5 seconds, meaning the effective timeout for this specific
case will be lowered and could theoretically pose problems under very
poor network conditions. Given we haven't felt the need to adjust the
5s transient activation timeout for bad networks yet, I suspect this
should be fine.
Bug: 1286053
Change-Id: I14a7b72e0f219fde8b4bdc59090a1a1a4b63508c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3379287
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Reviewed-by: Bo Liu <boliu@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Charles Reis <creis@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Cr-Commit-Position: refs/heads/main@{#958748}
6877c34aa9