Re: [w3c/payment-request] fix: restore transient activation requirement in show() (PR #1066)

marcoscaceres left a comment (w3c/payment-request#1066)

Thanks for the suggestions @stephenmcgruer and @ianbjacobs. I've updated the note to incorporate both — using "legacy" per Ian's suggestion, and keeping it implementation-neutral (not calling out Chromium specifically):

```html
<div class="note">
  Redirect flows can cause legitimate loss of transient activation
  before a call to {{PaymentRequest/show()}}. This is a known
  platform-wide problem affecting Payment Request, Digital
  Credentials, WebAuthn, and other APIs that require user
  activation. A general solution is being tracked in <a href=
  "https://github.com/w3c/payment-request/issues/1064">issue
  #1064</a>. Some user agents have legacy behavior that allows
  certain calls to {{PaymentRequest/show()}} without requiring
  user activation.
</div>
```

WDYT?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-request/pull/1066#issuecomment-4417399561
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/payment-request/pull/1066/c4417399561@github.com>