[w3c/browser-payment-api] Internal slots vs. attributes (#393)

I've been wondering for some time: Why are the `methodData`, `details` and `options` properties of the `PaymentRequest` interface defined as "internal slots" and not attributes? It's not that it doesn't work, or that there's any problem with having them as internal slots, I just found it weird. Is there a good reason for declaring these properties in this way?

If there is no good reason at all, then I would actually suggest changing them to attributes, as it would make the `PaymentRequest` structure a tiny bit easier to understand just by looking at the WebIDL.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/issues/393

Received on Tuesday, 10 January 2017 10:59:22 UTC