- From: ianbjacobs <notifications@github.com>
- Date: Tue, 13 Jun 2017 12:32:36 -0700
- To: w3c/payment-handler <payment-handler@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 13 June 2017 19:33:11 UTC
I agree the specification is lacking here. My understanding from our previous discussions is that: * As Rouslan indicates, we expected web apps to use web app manifest for app-level information. This is hinted at in the spec in the sentence "The user agent displays and groups these choices according to information (labels and icons) provided at registration or otherwise available from the Web app." The hint is not that helpful. * The instrument-level icons and names are not addressed by web app manifest and thus we define fields in this API. It seems we should add a sentence like the following to the spec (e.g., at the beginning of section 6 after the first paragraph). <p>This API defines mechanisms to specify icons and labels for the display of instruments. Other Web technology (e.g., Web app manifest) enables user agents to fetch icons, labels, and other "higher level" information about the payment handler.</p> Ian -- 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/payment-handler/issues/178#issuecomment-308223965
Received on Tuesday, 13 June 2017 19:33:11 UTC