Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(3)

Side by Side Diff: third_party/WebKit/Source/modules/payments/PaymentRequestUpdateEvent.idl

Issue 2697123003: Use ExecutionContext instead of Document in PaymentRequest constructor. (Closed)
Patch Set: Use ScriptState Created 3 years, 10 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
1 // Copyright 2016 The Chromium Authors. All rights reserved. 1 // Copyright 2016 The Chromium Authors. All rights reserved.
2 // Use of this source code is governed by a BSD-style license that can be 2 // Use of this source code is governed by a BSD-style license that can be
3 // found in the LICENSE file. 3 // found in the LICENSE file.
4 4
5 // https://w3c.github.io/browser-payment-api/#idl-def-paymentrequestupdateevent 5 // https://w3c.github.io/browser-payment-api/#idl-def-paymentrequestupdateevent
6 6
7 [ 7 [
8 RuntimeEnabled=PaymentRequest, 8 RuntimeEnabled=PaymentRequest,
9 Constructor(DOMString type, optional PaymentRequestUpdateEventInit eventInit Dict), 9 Constructor(DOMString type, optional PaymentRequestUpdateEventInit eventInit Dict),
10 ConstructorCallWith=ExecutionContext 10 ConstructorCallWith=ScriptState
please use gerrit instead 2017/02/19 18:53:02 Docs say that CallWith=ExecutionContext is depreca
Marijn Kruisselbrink 2017/02/21 19:08:56 Yep, seems that way. Although I'm very confused no
11 ] interface PaymentRequestUpdateEvent : Event { 11 ] interface PaymentRequestUpdateEvent : Event {
12 [CallWith=ScriptState,RaisesException] void updateWith(Promise<PaymentDetail s> d); 12 [CallWith=ScriptState,RaisesException] void updateWith(Promise<PaymentDetail s> d);
13 }; 13 };
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698