Re: [w3ctag/spec-reviews] PaymentRequest.canMakeActivePayment() (#146)

Ah, I found the discussion of "active" in https://github.com/w3c/browser-payment-api/issues/310 .  (Though I see substantial concern about the name there as well.)

I'm also curious how well this aligns with naming of other examples in the Web platform of functions returning promises that resolve to a boolean result.  The ones I found (from searching Gecko's WebIDL) are [<code>has</code> and <code>delete</code> on <code>CacheStorage</code>](https://www.w3.org/TR/service-workers/#cache-storage), [<code>remove</code> and <code>removeDeep</code> on <code>Directory</code>](http://w3c.github.io/filesystem-api/#idl-def-Directory), [<code>load</code> on <code>MediaKeySession</code>](http://w3c.github.io/encrypted-media/#idl-def-mediakeysession), [<code>unsubscribe</code> on <code>PushSubscription</code>](https://w3c.github.io/push-api/#pushsubscription-interface), [<code>unregister</code> on <code>ServiceWorkerRegistration</code>](https://www.w3.org/TR/service-workers/#service-worker-registration-interface), and [<code>persisted</code> and <code>persist</code> on <code>StorageManager</code>](https://storage.spec.whatwg.org/#storagemanager).  Of those, I think <code>has</code> is the only one that sounds like it returns a boolean.  (I guess the naming convention for functions returning promises should match the naming convention of synchronous functions, but it just feels weird in this case.  Maybe I'm just not used to it yet.)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/spec-reviews/issues/146#issuecomment-262405902