Re: [w3ctag/design-reviews] Payment Handler (#231)

I went through the responses above, and have a few comments on them:
* I'd still be interested in seeing a reaction to the points in the first paragraph of "Extensibility, permissions, and UI" in https://github.com/w3ctag/design-reviews/issues/231#issuecomment-377645336 -- in particular, whether the API offers enough information to present sufficient information to the user at the time of installing the payment handler, if user agents believe they should be more restrictive at install time?
* the biggest concern behind my question about "running the necessary level of detail through the API" was more about whether the issue of presenting content from the handler's UI inside of browser chrome was a workaround for deficiencies in the API.  I see that you've said that you think it's not feasible to avoid this -- but what happens if other browsers aren't comfortable with putting this content inside of browser chrome?  It seems like we're then stuck with very little information coming through the API.
* my concern about new mechanisms of communication was about whether this added capabilities to communicate across domains (e.g., through a service worker, i.e., allowing communication across domains when the user was interacting with only one of the sites) that didn't exist before.  I think @slightlyoff convinced me during the last (?) TAG face-to-face that this wasn't an issue, but I don't recall the details.  I think my concern was that this might be adding an ability to communicate data across origins *without* network traffic, which could possibly be used to do things like track users across domains without network traffic.
* I'm still concerned about some of the items in my "Other" section in https://github.com/w3ctag/design-reviews/issues/231#issuecomment-377645336 , especially the first item about specifying how these various Web Payment specifications relate to each other, e.g., the relationship between payment method identifiers and manifests.  Many of the other items there are details, but I'm curious if you've looked into them.
* I followed up in w3c/payment-handler#238; sorry for missing that earlier.

-- 
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/design-reviews/issues/231#issuecomment-405378011