Thanks all! FYI we are going to push this back a milestone to target M115 
to spend more time investigating improved spam mitigations (see design doc 
<https://docs.google.com/document/d/1DW4hGyuVzcN8sE8TC3YOkg6xO4XpUGZQNxcHgfMXVwA/edit#heading=h.9tic5lqm5god>
 security 
section).

Le mardi 25 avril 2023 à 11 h 30 min 44 s UTC-4, Mike Taylor a écrit :

> LGTM3
> On 4/25/23 11:05 AM, Yoav Weiss wrote:
>
> LGTM2
>
> On Tue, Apr 25, 2023 at 4:15 PM Rick Byers <[email protected]> wrote:
>
> This is a small behavior change to a shipped feature with no explicit API 
>> exposure. LGTM1
>>
>> On Wed, Apr 19, 2023 at 2:05 PM Nick Burris <[email protected]> wrote:
>>
> Le mercredi 19 avril 2023 à 03 h 45 min 37 s UTC-4, Yoav Weiss a écrit :
>>>
>>> On Mon, Apr 17, 2023 at 9:42 PM Nick Burris <[email protected]> 
>>> wrote:
>>>
>>> Contact [email protected], [email protected], 
>>> [email protected]
>>>
>>> Specificationhttps://github.com/w3c/secure-payment-confirmation/pull/236
>>>
>>> Design docshttps://docs.google.com/document/d/
>>> 1DW4hGyuVzcN8sE8TC3YOkg6xO4XpUGZQNxcHgfMXVwA
>>>
>>> Summary 
>>>
>>> To help developers reduce friction in Secure Payment Confirmation flows, 
>>> we are removing the user activation requirement. Spam and clickjacking 
>>> mitigations are put in place to mitigate security and privacy risks with 
>>> this change (see design doc 
>>> <https://docs.google.com/document/d/1DW4hGyuVzcN8sE8TC3YOkg6xO4XpUGZQNxcHgfMXVwA>
>>> ).
>>>
>>>
>>> Blink componentBlink>Payments 
>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EPayments>
>>>
>>> TAG reviewNone
>>>
>>> TAG review statusNot applicable
>>>
>>> Risks 
>>> Interoperability and Compatibility*Gecko*: No signal
>>>
>>> *WebKit*: No signal
>>>
>>>
>>> Have we asked for a signal? Are they shipping this feature?
>>>
>>>
>>> They have not shipped Secure Payment Confirmation as a whole, so we 
>>> don't have signals for this incremental change. We have open standards 
>>> positions issues for Gecko (mozilla/standards-positions/issues/570 
>>> <https://github.com/mozilla/standards-positions/issues/570>) and WebKit 
>>> (WebKit/standards-positions/issues/30 
>>> <https://github.com/WebKit/standards-positions/issues/30>).
>>>  
>>>
>>
>>> *Web developers*: We've received direct feedback from web developers 
>>> that they would be able to reduce friction in their redirect-based payment 
>>> flows if SPC could be initiated without a user activation.
>>>
>>> *Other signals*:
>>>
>>> WebView application risks 
>>>
>>> Does this intent deprecate or change behavior of existing APIs, such 
>>> that it has potentially high risk for Android WebView-based applications?
>>>
>>> None
>>>
>>>
>>> DebuggabilityExisting debuggability for SPC; e.g. a specific 
>>> SecurityError is thrown when an activationless show() call is not allowed 
>>> (see this test page 
>>> <https://rsolomakhin.github.io/pr/spc-activationless/>).
>>>
>>>
>>>
>>> Will this feature be supported on all six Blink platforms (Windows, Mac, 
>>> Linux, Chrome OS, Android, and Android WebView)?No, only features where 
>>> SPC is already shipped: Windows, Mac, Android
>>>
>>> Is this feature fully tested by web-platform-tests 
>>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
>>> ?Yes 
>>> <https://wpt.fyi/results/secure-payment-confirmation/authentication-requires-user-activation.https.html?label=experimental&label=master&aligned>
>>>  (to 
>>> be updated with implementation)
>>>
>>> Flag name--enable-blink-features=SecurePaymentConfirmationActiv
>>> ationlessShow
>>>
>>> Requires code in //chrome?False
>>>
>>> Estimated milestonesShipping on desktop114Shipping on Android114
>>>
>>> Anticipated spec changes
>>> https://github.com/w3c/secure-payment-confirmation/pull/236
>>>
>>> Link to entry on the Chrome Platform Statushttps://chromestatus.com/
>>> feature/5197059260416000
>>>
>>> This intent message was generated by Chrome Platform Status 
>>> <https://chromestatus.com/>.
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "blink-dev" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to [email protected].
>>> To view this discussion on the web visit https://groups.google.com/a/
>>> chromium.org/d/msgid/blink-dev/CADvKJHN9Rp4gYYZJ4Jx9iwMiA3jS%
>>> 2BagC_7L5dWkEGrWo8OLX4w%40mail.gmail.com 
>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADvKJHN9Rp4gYYZJ4Jx9iwMiA3jS%2BagC_7L5dWkEGrWo8OLX4w%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "blink-dev" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to [email protected].
>>> To view this discussion on the web visit 
>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6fd8eabf-2e7e-4af3-94cf-57fe5a555483n%40chromium.org
>>>  
>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6fd8eabf-2e7e-4af3-94cf-57fe5a555483n%40chromium.org?utm_medium=email&utm_source=footer>
>>> .
>>>
>> -- 
> You received this message because you are subscribed to the Google Groups 
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
>
> To view this discussion on the web visit 
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfW3R7Ax-OYG7nu9%3DBOW6n5vBM6QFzTYdtMuxvZWJW8%3DKA%40mail.gmail.com
>  
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfW3R7Ax-OYG7nu9%3DBOW6n5vBM6QFzTYdtMuxvZWJW8%3DKA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/fa21f66a-0aec-45b7-95e3-df4fc9074f1cn%40chromium.org.

Reply via email to