w3c/payment-handler Issues

Last updated Nov 21, 2024, 5:55:34 AM UTC.

This repository doesn't have the Priority: Eventually label that's used to mark an issue as triaged without giving it an SLO. Until that's added, this summary uses heuristics to guess if each issue has been triaged.

Untriaged

Try to triage issues within . [ More Info ]

Issue Title Within SLO On maintainers' plates for Time left Time past SLO
#203 Make explicit which origin to use in conjunction with payment method manifest ❌
#232 PaymentInstruments' "the collection" needs an internal slot. ❌
#234 retrieving the permission state ❌
#255 PaymentInstruments is missing values() and entries() ❌
#256 PaymentInstruments internal storage could be clearer ❌
#257 Do not use "context object" ❌
#258 Integrate better with the payment request spec ❌
#261 Get rid of normative requirements inside dictionary member definitions ❌
#264 Editorial tweaks to " MethodData Population Algorithm" ❌
#265 Structured clone usage seems wrong ❌
#266 "Dispatch e to global" should link ❌
#306 Add support for PaymentValidationErrors ❌
#312 Add paymentRequestID to CanMakePaymentEvent? ❌
#321 Update Open Window Algorithm ❌
#347 Specify skip-the-sheet behavior ❌
#360 Add informative mention of native payment handlers ❌
#362 See W3C TAG review comments ❌
#364 Rename canmakepayment event to hasenrolledinstrument event ❌
#378 Leftovers regarding modifiers in CanMakePaymentEvents ❌
#380 Require user gesture before installation payment app that supports a standardized payment method? ❌
#395 Updates for respec ❌
#405 WPT test suite needs updating to match spec + implementations ❌
#416 Reduce risk of tracking related to payment handlers without UI ❌
#419 Missing tasks in parallel steps in Payment Handler API ❌