Need a consistent set of events that defines user activation #3849

mustaqahmed · 2018-07-24T18:54:57Z

This is related to #1903, where we are working on a user activation model. Here I am isolating the discussion on "events that should trigger a user activation" because this looks like a parallel work that can go ahead with or without the model question.

Current Activation section mentions (among other things) a list of activation triggering events. Unfortunately the list doesn't represent the reality. A recent catalog of activation-triggering events in Chrome, Edge, Firefox and Safari shows the big inconsistencies we have today, sometimes even between desktop and mobile versions of the same browser.

We need to fix this.

One challenging point is the possibility that the set of events could be API-specific!

mustaqahmed · 2018-07-24T18:59:48Z

Chromium bug to track this: https://crbug.com/826293

RByers · 2018-10-22T13:13:26Z

FWIW, I'm convinced by the argument here that in addition to a standardized list of events, we should have some single API to be informed of when frame has been activated (to prevent developers from having to maintain a hard-coded list of events, etc.).

In particular, the use case of starting the background music for a game is a good one - it's reasonable to want to do that as soon as the user has indicated any interaction, without necessarily caring what exact form that interaction comes in (eg. launching a PWA, or pressing a gamepad button which fires no dom events at all).

RByers · 2018-10-23T11:30:32Z

Sorry, I missed @mustaqahmed's response in the WICG thread on this. Let's discuss this particular issue there in the WICG and come back here with any concrete proposal.

domenic · 2021-09-21T22:59:38Z

This interop problem remains. I recently wrote some web platform tests that assumed pressing keys (using testdriver) was an activation-triggering event, but that was not correct according to the spec, even though it was true in Chrome.

#6818 by @marcoscaceres is related; he is trying to add keypress and keyup, which at least according to @mustaqahmed's OP is a pretty complicated situation across browsers.

For keyboard events in particular, there is a big question as to what should count. E.g. in WICG/close-watcher#7 (comment) we are discussing whether the Esc key should count as user activation. Consider a user who visits a page, and all they do is press Esc; should that let the page show popups or play unmuted video or enter fullscreen??

mustaqahmed · 2021-09-22T13:37:10Z

In Chrome, we stopped counting Esc key as a user activation to fix a security bug a while ago.

[Edit: fixed the link above!]

mustaqahmed · 2021-10-01T20:56:54Z

Let's explore a way to fix the overall mess here. I am proposing to address the following three sub-problems independently, please let us know your thoughts on each of these (and possibly other) cases.

A. Drop all high-level events

This should be the easiest one I believe: the current list of events include "high-level" events like submit because before User Activation v2, the user activation from a mousedown/keydown was not usable in a submit event-handler. This is no longer the case now, so we can drop all of them.

B. Fine-tune low-level events

The list logically omits touchstart (because a swipe is not a user activation and we can't identify a swipe at touchstart). But why is mousedown also omitted? I vaguely remember Chrome facing compat problems when trying to remove mousedown activation. What about other browsers?

What other low-level events do we need to consider? What about pointerdown?

C. Keyboard event trigger should be key-specific

It seems we reached the consensus that Esc key shouldn't activate the page (right?). Similarly, both Chrome (bug) and Firefox (bug) want to make browser hotkeys like ctrl-W or alt-LeftArrow non-activating. Which other keys fall in the same category? Should del and backspace keys activate or not?

To test your favorite browser's behavior, you can try (or tweak) the "control case" in this repro.

annevk · 2021-10-12T08:42:56Z

Overall that sounds reasonable to me. Probably any kind of browser accesskey you wouldn't want to count as activation? E.g., command+tab shouldn't result in a popup, it should result in a new browser tab.

cc @EdgarChen @johannhof

domenic · 2021-10-12T19:51:03Z

Agreed, that plan sounds great to me.

eric-carlson · 2021-10-12T20:50:28Z

B. Fine-tune low-level events

The list logically omits touchstart (because a swipe is not a user activation and we can't identify a swipe at touchstart). But why is mousedown also omitted? I vaguely remember Chrome facing compat problems when trying to remove mousedown activation. What about other browsers?

We also found compatibility problems when we tried to remove mousedown activation from WebKit.

Apple's WebKit port also includes touchstart activation, but only for media playback. We also tried to remove this at one point, but there were too many compatibility problems.

mustaqahmed · 2021-10-20T16:24:08Z

I just sent out PR #7248, please take a look.

This PR addressed A, B and most part of C in my plan above. I realized that my original plan (to independently fix the sub-problems) won't work because removing click (for sub-problem A) would leave a gaping hole around keyboard activation!

Related to HTML issue: whatwg/html#3849 Also fix double-activation in Chrome's gesture tap. Bug: 826293, 1265587 Change-Id: I3bc3bcbcfeda242512fb777a1c8881c475fed5fc

Related to HTML issue: whatwg/html#3849 Also fix double-activation in Chrome's gesture tap. Bug: 826293, 1265587 Change-Id: I3bc3bcbcfeda242512fb777a1c8881c475fed5fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3254213 Reviewed-by: Robert Flack <[email protected]> Reviewed-by: Avi Drissman <[email protected]> Commit-Queue: Mustaq Ahmed <[email protected]> Cr-Commit-Position: refs/heads/main@{#940118}

This reverts commit 34b3146d8dfc1e44715703e4cf97779fc7c8688d. Reason for revert: Suspected cause of crbug.com/1269035, will verify before submitting. Original change's description: > Add a WPT for pointerevent user activation trigger. > > Related to HTML issue: whatwg/html#3849 > > Also fix double-activation in Chrome's gesture tap. > > Bug: 826293, 1265587 > Change-Id: I3bc3bcbcfeda242512fb777a1c8881c475fed5fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3254213 > Reviewed-by: Robert Flack <[email protected]> > Reviewed-by: Avi Drissman <[email protected]> > Commit-Queue: Mustaq Ahmed <[email protected]> > Cr-Commit-Position: refs/heads/main@{#940118} # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 826293, 1265587 Change-Id: I4bc041f2254c382c00ce3596d61742ba84c79660

This reverts commit 34b3146d8dfc1e44715703e4cf97779fc7c8688d. Reason for revert: Suspected cause of crbug.com/1269035, will verify before submitting. Original change's description: > Add a WPT for pointerevent user activation trigger. > > Related to HTML issue: whatwg/html#3849 > > Also fix double-activation in Chrome's gesture tap. > > Bug: 826293, 1265587 > Change-Id: I3bc3bcbcfeda242512fb777a1c8881c475fed5fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3254213 > Reviewed-by: Robert Flack <[email protected]> > Reviewed-by: Avi Drissman <[email protected]> > Commit-Queue: Mustaq Ahmed <[email protected]> > Cr-Commit-Position: refs/heads/main@{#940118} # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 826293, 1265587 Change-Id: I4bc041f2254c382c00ce3596d61742ba84c79660 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3277061 Reviewed-by: Brian Sheedy <[email protected]> Reviewed-by: Johann Koenig <[email protected]> Commit-Queue: Brian Sheedy <[email protected]> Commit-Queue: Johann Koenig <[email protected]> Owners-Override: Johann Koenig <[email protected]> Cr-Commit-Position: refs/heads/main@{#940996}

This reverts commit 34b3146. Reason for revert: Suspected cause of crbug.com/1269035, will verify before submitting. Original change's description: > Add a WPT for pointerevent user activation trigger. > > Related to HTML issue: whatwg/html#3849 > > Also fix double-activation in Chrome's gesture tap. > > Bug: 826293, 1265587 > Change-Id: I3bc3bcbcfeda242512fb777a1c8881c475fed5fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3254213 > Reviewed-by: Robert Flack <[email protected]> > Reviewed-by: Avi Drissman <[email protected]> > Commit-Queue: Mustaq Ahmed <[email protected]> > Cr-Commit-Position: refs/heads/main@{#940118} # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 826293, 1265587 Change-Id: I4bc041f2254c382c00ce3596d61742ba84c79660 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3277061 Reviewed-by: Brian Sheedy <[email protected]> Reviewed-by: Johann Koenig <[email protected]> Commit-Queue: Brian Sheedy <[email protected]> Commit-Queue: Johann Koenig <[email protected]> Owners-Override: Johann Koenig <[email protected]> Cr-Commit-Position: refs/heads/main@{#940996}

Related to HTML issue: whatwg/html#3849 Bug: 826293 Change-Id: I9e4bc0df46df63e05dac64af32c1aab7cdabffe4

…on trigger., a=testonly Automatic update from web-platform-tests Add a WPT for pointerevent user activation trigger. Related to HTML issue: whatwg/html#3849 Also fix double-activation in Chrome's gesture tap. Bug: 826293, 1265587 Change-Id: I3bc3bcbcfeda242512fb777a1c8881c475fed5fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3254213 Reviewed-by: Robert Flack <[email protected]> Reviewed-by: Avi Drissman <[email protected]> Commit-Queue: Mustaq Ahmed <[email protected]> Cr-Commit-Position: refs/heads/main@{#940118} -- wpt-commits: aa2fc4c2ddfac8b0870c0b075899478c9cabc0c2 wpt-pr: 31521

…activation trigger.", a=testonly Automatic update from web-platform-tests Revert "Add a WPT for pointerevent user activation trigger." This reverts commit 34b3146d8dfc1e44715703e4cf97779fc7c8688d. Reason for revert: Suspected cause of crbug.com/1269035, will verify before submitting. Original change's description: > Add a WPT for pointerevent user activation trigger. > > Related to HTML issue: whatwg/html#3849 > > Also fix double-activation in Chrome's gesture tap. > > Bug: 826293, 1265587 > Change-Id: I3bc3bcbcfeda242512fb777a1c8881c475fed5fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3254213 > Reviewed-by: Robert Flack <[email protected]> > Reviewed-by: Avi Drissman <[email protected]> > Commit-Queue: Mustaq Ahmed <[email protected]> > Cr-Commit-Position: refs/heads/main@{#940118} # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 826293, 1265587 Change-Id: I4bc041f2254c382c00ce3596d61742ba84c79660 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3277061 Reviewed-by: Brian Sheedy <[email protected]> Reviewed-by: Johann Koenig <[email protected]> Commit-Queue: Brian Sheedy <[email protected]> Commit-Queue: Johann Koenig <[email protected]> Owners-Override: Johann Koenig <[email protected]> Cr-Commit-Position: refs/heads/main@{#940996} -- wpt-commits: eca3a50a442ab21283638efbf1617492924f5fdd wpt-pr: 31608

…on trigger., a=testonly Automatic update from web-platform-tests Add a WPT for pointerevent user activation trigger. Related to HTML issue: whatwg/html#3849 Also fix double-activation in Chrome's gesture tap. Bug: 826293, 1265587 Change-Id: I3bc3bcbcfeda242512fb777a1c8881c475fed5fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3254213 Reviewed-by: Robert Flack <[email protected]> Reviewed-by: Avi Drissman <[email protected]> Commit-Queue: Mustaq Ahmed <[email protected]> Cr-Commit-Position: refs/heads/main@{#940118} -- wpt-commits: aa2fc4c2ddfac8b0870c0b075899478c9cabc0c2 wpt-pr: 31521

…activation trigger.", a=testonly Automatic update from web-platform-tests Revert "Add a WPT for pointerevent user activation trigger." This reverts commit 34b3146d8dfc1e44715703e4cf97779fc7c8688d. Reason for revert: Suspected cause of crbug.com/1269035, will verify before submitting. Original change's description: > Add a WPT for pointerevent user activation trigger. > > Related to HTML issue: whatwg/html#3849 > > Also fix double-activation in Chrome's gesture tap. > > Bug: 826293, 1265587 > Change-Id: I3bc3bcbcfeda242512fb777a1c8881c475fed5fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3254213 > Reviewed-by: Robert Flack <[email protected]> > Reviewed-by: Avi Drissman <[email protected]> > Commit-Queue: Mustaq Ahmed <[email protected]> > Cr-Commit-Position: refs/heads/main@{#940118} # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 826293, 1265587 Change-Id: I4bc041f2254c382c00ce3596d61742ba84c79660 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3277061 Reviewed-by: Brian Sheedy <[email protected]> Reviewed-by: Johann Koenig <[email protected]> Commit-Queue: Brian Sheedy <[email protected]> Commit-Queue: Johann Koenig <[email protected]> Owners-Override: Johann Koenig <[email protected]> Cr-Commit-Position: refs/heads/main@{#940996} -- wpt-commits: eca3a50a442ab21283638efbf1617492924f5fdd wpt-pr: 31608

Related to HTML issue: whatwg/html#3849 Bug: 826293 Change-Id: I9e4bc0df46df63e05dac64af32c1aab7cdabffe4

Related to HTML issue: whatwg/html#3849 Bug: 826293 Change-Id: I9e4bc0df46df63e05dac64af32c1aab7cdabffe4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3282485 Commit-Queue: Mustaq Ahmed <[email protected]> Reviewed-by: Robert Flack <[email protected]> Cr-Commit-Position: refs/heads/main@{#942663}

Related to HTML issue: whatwg/html#3849 Bug: 826293 Change-Id: I9e4bc0df46df63e05dac64af32c1aab7cdabffe4

Related to HTML issue: whatwg/html#3849 Bug: 826293 Change-Id: I9e4bc0df46df63e05dac64af32c1aab7cdabffe4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3282485 Commit-Queue: Mustaq Ahmed <[email protected]> Reviewed-by: Robert Flack <[email protected]> Cr-Commit-Position: refs/heads/main@{#942663}

Related to HTML issue: whatwg/html#3849 Also fix double-activation in Chrome's gesture tap. Bug: 826293, 1265587 Change-Id: I3bc3bcbcfeda242512fb777a1c8881c475fed5fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3254213 Reviewed-by: Robert Flack <[email protected]> Reviewed-by: Avi Drissman <[email protected]> Commit-Queue: Mustaq Ahmed <[email protected]> Cr-Commit-Position: refs/heads/main@{#940118}

This reverts commit 34b3146d8dfc1e44715703e4cf97779fc7c8688d. Reason for revert: Suspected cause of crbug.com/1269035, will verify before submitting. Original change's description: > Add a WPT for pointerevent user activation trigger. > > Related to HTML issue: whatwg/html#3849 > > Also fix double-activation in Chrome's gesture tap. > > Bug: 826293, 1265587 > Change-Id: I3bc3bcbcfeda242512fb777a1c8881c475fed5fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3254213 > Reviewed-by: Robert Flack <[email protected]> > Reviewed-by: Avi Drissman <[email protected]> > Commit-Queue: Mustaq Ahmed <[email protected]> > Cr-Commit-Position: refs/heads/main@{#940118} # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 826293, 1265587 Change-Id: I4bc041f2254c382c00ce3596d61742ba84c79660 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3277061 Reviewed-by: Brian Sheedy <[email protected]> Reviewed-by: Johann Koenig <[email protected]> Commit-Queue: Brian Sheedy <[email protected]> Commit-Queue: Johann Koenig <[email protected]> Owners-Override: Johann Koenig <[email protected]> Cr-Commit-Position: refs/heads/main@{#940996}

Related to HTML issue: whatwg/html#3849 Bug: 826293 Change-Id: I9e4bc0df46df63e05dac64af32c1aab7cdabffe4

…on trigger., a=testonly Automatic update from web-platform-tests Add a WPT for pointerevent user activation trigger. Related to HTML issue: whatwg/html#3849 Bug: 826293 Change-Id: I9e4bc0df46df63e05dac64af32c1aab7cdabffe4 -- wpt-commits: 266273172093e63a85e72b184735342d5c298797 wpt-pr: 31632

* Remove all high-level events that follows a low-level event. * Add missing low-level events that are known to be required. * Add keyboard events, in a conditional manner. Fixes whatwg#3849.

Related to HTML issue: whatwg/html#3849 Also fix double-activation in Chrome's gesture tap. Bug: 826293, 1265587 Change-Id: I3bc3bcbcfeda242512fb777a1c8881c475fed5fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3254213 Reviewed-by: Robert Flack <[email protected]> Reviewed-by: Avi Drissman <[email protected]> Commit-Queue: Mustaq Ahmed <[email protected]> Cr-Commit-Position: refs/heads/main@{#940118} NOKEYCHECK=True GitOrigin-RevId: 34b3146d8dfc1e44715703e4cf97779fc7c8688d

This reverts commit 34b3146d8dfc1e44715703e4cf97779fc7c8688d. Reason for revert: Suspected cause of crbug.com/1269035, will verify before submitting. Original change's description: > Add a WPT for pointerevent user activation trigger. > > Related to HTML issue: whatwg/html#3849 > > Also fix double-activation in Chrome's gesture tap. > > Bug: 826293, 1265587 > Change-Id: I3bc3bcbcfeda242512fb777a1c8881c475fed5fc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3254213 > Reviewed-by: Robert Flack <[email protected]> > Reviewed-by: Avi Drissman <[email protected]> > Commit-Queue: Mustaq Ahmed <[email protected]> > Cr-Commit-Position: refs/heads/main@{#940118} # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 826293, 1265587 Change-Id: I4bc041f2254c382c00ce3596d61742ba84c79660 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3277061 Reviewed-by: Brian Sheedy <[email protected]> Reviewed-by: Johann Koenig <[email protected]> Commit-Queue: Brian Sheedy <[email protected]> Commit-Queue: Johann Koenig <[email protected]> Owners-Override: Johann Koenig <[email protected]> Cr-Commit-Position: refs/heads/main@{#940996} NOKEYCHECK=True GitOrigin-RevId: 9872337b36442fa626dad89cee80f77fdd41fb30

Related to HTML issue: whatwg/html#3849 Bug: 826293 Change-Id: I9e4bc0df46df63e05dac64af32c1aab7cdabffe4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3282485 Commit-Queue: Mustaq Ahmed <[email protected]> Reviewed-by: Robert Flack <[email protected]> Cr-Commit-Position: refs/heads/main@{#942663} NOKEYCHECK=True GitOrigin-RevId: 5a60aab31ba136dae6cd61b0e48cb753929b1051

domenic mentioned this issue Jul 30, 2018

User activation: different concepts for different usages #3859

Closed

zcorpan added the topic: events label Sep 1, 2018

mustaqahmed mentioned this issue Sep 27, 2018

Added a new section on User Activation v2. #3851

Merged

mustaqahmed mentioned this issue Mar 20, 2019

User Activation Delegation through postMessages w3ctag/design-reviews#347

Closed

5 tasks

annevk added the topic: user activation label Jun 28, 2019

chrisosaurus mentioned this issue Sep 2, 2020

Element activation and synthesized events WICG/aom#168

Open

mkruisselbrink mentioned this issue Feb 4, 2021

Feedback: User Activation unpredictable for IndexDB loaded handler permissions WICG/file-system-access#246

Closed

mkruisselbrink mentioned this issue Feb 16, 2021

Launching a PWA should qualify as a "User activation" WICG/file-system-access#274

Closed

domenic mentioned this issue Sep 21, 2021

Should the Esc key count as user activation? WICG/close-watcher#7

Closed

This was referenced Sep 28, 2021

interactionID should be harmonized with activation triggering input events w3c/event-timing#105

Closed

Add 'keyup' and 'keypress' to 'activation triggering input event' #6818

Closed

mustaqahmed mentioned this issue Oct 20, 2021

Update the list of activation triggering input events #7248

Merged

3 tasks

domenic closed this as completed in 56071d6 Nov 1, 2021

chromium-wpt-export-bot mentioned this issue Nov 5, 2021

Add a WPT for pointerevent user activation trigger. web-platform-tests/wpt#31521

Merged

chromium-wpt-export-bot mentioned this issue Nov 11, 2021

Revert "Add a WPT for pointerevent user activation trigger." web-platform-tests/wpt#31608

Merged

chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this issue Nov 15, 2021

Add a WPT for pointerevent user activation trigger.

e828c2d

Related to HTML issue: whatwg/html#3849 Bug: 826293 Change-Id: I9e4bc0df46df63e05dac64af32c1aab7cdabffe4

chromium-wpt-export-bot mentioned this issue Nov 15, 2021

Add a WPT for pointerevent user activation trigger. web-platform-tests/wpt#31632

Merged

flackr mentioned this issue Nov 16, 2021

Can we make user activation consistent between pointer types? #7341

Open

chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this issue Nov 17, 2021

Add a WPT for pointerevent user activation trigger.

458b2fb

Related to HTML issue: whatwg/html#3849 Bug: 826293 Change-Id: I9e4bc0df46df63e05dac64af32c1aab7cdabffe4

chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this issue Nov 17, 2021

Add a WPT for pointerevent user activation trigger.

cff8a61

Related to HTML issue: whatwg/html#3849 Bug: 826293 Change-Id: I9e4bc0df46df63e05dac64af32c1aab7cdabffe4

chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this issue Nov 17, 2021

Add a WPT for pointerevent user activation trigger.

2662731

Related to HTML issue: whatwg/html#3849 Bug: 826293 Change-Id: I9e4bc0df46df63e05dac64af32c1aab7cdabffe4

Gabisampaio pushed a commit to Gabisampaio/wpt that referenced this issue Nov 18, 2021

Add a WPT for pointerevent user activation trigger.

3bf0ee6

Related to HTML issue: whatwg/html#3849 Bug: 826293 Change-Id: I9e4bc0df46df63e05dac64af32c1aab7cdabffe4

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Need a consistent set of events that defines user activation #3849

Need a consistent set of events that defines user activation #3849

mustaqahmed commented Jul 24, 2018

mustaqahmed commented Jul 24, 2018

RByers commented Oct 22, 2018 •

edited

Loading

RByers commented Oct 23, 2018

domenic commented Sep 21, 2021

mustaqahmed commented Sep 22, 2021 •

edited

Loading

mustaqahmed commented Oct 1, 2021

annevk commented Oct 12, 2021

domenic commented Oct 12, 2021

eric-carlson commented Oct 12, 2021

B. Fine-tune low-level events

mustaqahmed commented Oct 20, 2021

Need a consistent set of events that defines user activation #3849

Need a consistent set of events that defines user activation #3849

Comments

mustaqahmed commented Jul 24, 2018

mustaqahmed commented Jul 24, 2018

RByers commented Oct 22, 2018 • edited Loading

RByers commented Oct 23, 2018

domenic commented Sep 21, 2021

mustaqahmed commented Sep 22, 2021 • edited Loading

mustaqahmed commented Oct 1, 2021

A. Drop all high-level events

B. Fine-tune low-level events

C. Keyboard event trigger should be key-specific

annevk commented Oct 12, 2021

domenic commented Oct 12, 2021

eric-carlson commented Oct 12, 2021

B. Fine-tune low-level events

mustaqahmed commented Oct 20, 2021

RByers commented Oct 22, 2018 •

edited

Loading

mustaqahmed commented Sep 22, 2021 •

edited

Loading