User activation API #4009

dtapuska · 2018-09-06T19:24:13Z

This pull request builds on other pull requests. Specifically:
#3800
#3851

Please ignore the first two commits since they are reflective of the other pull requests.

💥 Error: Wattsi server error 💥

PR Preview failed to build. (Last tried on Jan 15, 2021, 7:58 AM UTC).

More

PR Preview relies on a number of web services to run. There seems to be an issue with the following one:

🚨 Wattsi Server - Wattsi Server is the web service used to build the WHATWG HTML spec.

🔗 Related URL

Command failed: /home/noderunner/wattsi/bin/wattsi /tmp/upload_f4019edeaf4803185b60a27060bae86d (sha not provided) wc3hssvfxkg default /tmp/upload_17c16a3cd38181289b0b9d045612cecc

If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please file an issue.

dtapuska · 2018-09-06T19:30:15Z

Cross referencing TAG request w3ctag/design-reviews#300

dtapuska · 2018-09-11T16:29:23Z

@cdumez @smaug---- @travisleithead

Are other vendors interested in this design for exposing UserActivation information?

foolip · 2018-09-28T13:24:49Z

source

+    user is currently interacting with <var>W</var> or its subframes.  The flag is set every time
+    <var>W</var> is <span data-x="activates-a-window">activated</span>, and is reset either
+      <ul>
+        <li>after an expiry time defined by the browser, or</li>


I'm wondering whether it will be possible for the transient activation flag to change its value during scrip execution, so that if (event.userActivation.isActive) { console.log(event.userActivation.isActive) } is guaranteed to log true? It could be a rare and hard-to-reproduce race condition if this is not guaranteed. On the other hand, guaranteeing it would mean that busy-waiting could allow the action to be delayed beyond the expiry time, and that's not a good incentive at all.

This depends on how this step is implemented, and the most straightforward implementation would probably involve an internal equivalent of setTimeout that can't run in the middle of a script. @dtapuska, do you think anything should be said here, either for implementers to uphold the guarantee, or that the guarantee doesn't exist?

The event user actviation API is a snapshot.

For navigator.userActivation it is a live object and it is possible. With a timeout API there will always be a race.

Another alternate is that you expose the timestamp of the last transient user activation. But the problem with that is you don't know what timeout the user agent uses.

dtapuska · 2018-10-15T13:34:25Z

@cdumez @smaug---- @travisleithead

I tried to solicit opinions a month ago have you been able to look at this proposal?

mustaqahmed · 2019-10-15T19:16:39Z

The navigator interface proposed here came up last month during our TPAC session on User Activation v2. There was consensus that this interface would be useful for testing UAv2: we want to be able to write web-platform-tests for user activation core without relying on other high-level APIs (that are gated by user activation), otherwise the tests would be affected by cross-browser differences in those high-level APIs.

There was also a brief discussion about using this interface to conditionally show a button "click here to ..." if transient activation expired because, say, the user spent too long in a file upload dialog.

@annevk @smaug---- @whsieh: please review this PR for the JS exposed state we need for UAv2 testing.

annevk

Overall this seems reasonable, but there are quite a few details that need tighter language. We also need a lot of test coverage to address all the various postMessage() APIs (might also require changes to service workers).

annevk · 2019-10-22T14:17:23Z

source

+  data-x="dom-MessageEvent-userActivation">userActivation</code> attribute will be snapshot objects,
+  that is a snapshot of the source's state.</p>
+
+  <pre><code class="idl" data-x="">[Exposed=(Window,Worker,AudioWorklet)]


Does an AudioWorklet need this? Other worklets don't?

This matches what MessageEvent is defined in. Is MessageEvent wrong?

No that's correct, but does it make sense to message user activation to an audio worklet? Does it mean anything?

source

annevk · 2019-10-22T14:18:14Z

source

@@ -73409,6 +73409,74 @@ END:VCARD</pre>
  </ul>


+  <h4>The <code>UserActivation</code> interface</h4>
+
+  <p>The <span>user activation state</span> is provided via the <code>UserActivation</code>


What's the reason to not make this a mixin of sorts?

I don't really follow which object we are talking about here. The partial interface on the Navigator?

Yeah, as it's also needed on the event, but I think it's probably for the best this way. We should put this directly on Navigator though.

Also, can you pass user activation into a worker, should this be exposed on WorkerNavigator?

Re a state in WorkerNavigator: I think a such state would be unnecessary:

A worker cannot have a UI surface where user can interact with it directly, right? So it cannot ever have its own user activation.

The idea of passing user activation state from the main thread to a worker (so that the worker can now open popups etc) is very thorny. We took back a past proposal for state delegation between iframes because we heard strong (and logical) pushback from security and privacy perspectives. And a worker is way more hidden/obscure to an end-user than an iframe!

Would it then not make more sense to only have it on WindowPostMessageOptions? Presumably passing it to a background tab is also not ideal?

annevk · 2019-10-22T14:18:42Z

source

+  <div w-nodev>
+
+  <p>The <dfn><code data-x="dom-UserActivation-hasBeenActive">hasBeenActive</code></dfn> attribute
+  must return the state of the <span>sticky activation flag</span>. If the object is live it must


Please get the flag from an object of sorts.

I don't follow this comment. The UserActivation object could be a snapshot in time or a live variation. I guess that can be kind of odd.

I meant that it's unclear where "sticky activation flag" comes from.

annevk · 2019-10-22T14:21:08Z

source

+     <var>messageClone</var>, the <code data-x="dom-MessageEvent-ports">ports</code> attribute
+     initialized to <var>newPorts</var>, and the <code
+     data-x="dom-MessageEvent-userActivation">userActivation</code> attribute initialized to
+     <var>userActivationSnapshot</var>.</p></li>


Aren't you accessing an object created in potentially a different process here? I don't think that works.

How do we define this object as it serializes?

I'm not sure I understand the question. Could you elaborate?

Describe the interface and augment PostMessage options to contain the required fields. Fixes whatwg#4008

mustaqahmed · 2022-09-08T18:02:15Z

I forked off only the navigator part of this PR into #8254

sideshowbarker mentioned this pull request Sep 11, 2018

JS API for querying user activation w3c/strategy#140

Closed

foolip mentioned this pull request Sep 18, 2018

Media: add method to discover whether playback is allowed before calling play() #3617

Closed

foolip reviewed Sep 28, 2018

View reviewed changes

dtapuska mentioned this pull request Feb 7, 2019

User Activation API w3ctag/design-reviews#300

Closed

5 tasks

mustaqahmed mentioned this pull request Mar 8, 2019

User Activation: ability to transfer activation to another frame #4364

Closed

dtapuska force-pushed the user_activation branch from 26fb706 to 826eb51 Compare October 15, 2019 19:31

annevk reviewed Oct 22, 2019

View reviewed changes

dtapuska force-pushed the user_activation branch from 826eb51 to a2e893c Compare November 7, 2019 19:12

dtapuska force-pushed the user_activation branch from a2e893c to 9f94fe3 Compare December 12, 2019 15:13

Add user activation interface.

e7012cb

Describe the interface and augment PostMessage options to contain the required fields. Fixes whatwg#4008

dtapuska force-pushed the user_activation branch from 9f94fe3 to e7012cb Compare December 12, 2019 15:27

mustaqahmed mentioned this pull request Jan 13, 2020

Set requests' user activation flag during navigation. #5203

Merged

3 tasks

annevk mentioned this pull request Jun 9, 2020

Add ability to query UserActivation state #4008

Closed

Base automatically changed from master to main January 15, 2021 07:57

domenic force-pushed the main branch from 0947339 to 1b5099f Compare July 27, 2021 17:07

annevk mentioned this pull request Oct 6, 2021

Draft for Autoplay Detection spec w3c/autoplay#14

Merged

past mentioned this pull request Feb 3, 2022

Upcoming HTML standard issue triage meeting on 2/3/2022 #7488

Closed

mustaqahmed mentioned this pull request Sep 8, 2022

Add a navigator interface for user activation state. #8254

Merged

3 tasks

domenic closed this in 823a14b Sep 14, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

User activation API #4009

User activation API #4009

dtapuska commented Sep 6, 2018 •

edited by pr-preview bot

Loading

dtapuska commented Sep 6, 2018

dtapuska commented Sep 11, 2018

foolip Sep 28, 2018

dtapuska Sep 28, 2018

dtapuska commented Oct 15, 2018

mustaqahmed commented Oct 15, 2019

annevk left a comment

annevk Oct 22, 2019

dtapuska Dec 12, 2019

annevk Jan 10, 2020

annevk Oct 22, 2019

dtapuska Dec 12, 2019

annevk Jan 10, 2020

mustaqahmed Jan 10, 2020

annevk Jan 10, 2020

annevk Oct 22, 2019

dtapuska Dec 12, 2019

annevk Jan 10, 2020

annevk Oct 22, 2019

dtapuska Dec 12, 2019

annevk Jan 10, 2020

mustaqahmed commented Sep 8, 2022

User activation API #4009

User activation API #4009

Conversation

dtapuska commented Sep 6, 2018 • edited by pr-preview bot Loading

💥 Error: Wattsi server error 💥

dtapuska commented Sep 6, 2018

dtapuska commented Sep 11, 2018

Choose a reason for hiding this comment

Choose a reason for hiding this comment

dtapuska commented Oct 15, 2018

mustaqahmed commented Oct 15, 2019

annevk left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mustaqahmed commented Sep 8, 2022

dtapuska commented Sep 6, 2018 •

edited by pr-preview bot

Loading