Should Payment Request enable optional Total for some use cases?
Open
Nobody has claimed this yet.
Future Candidate Feature
- Dominant language
- HTML
- Stars
- 510
- Forks
- 139
- PR merge metrics
- No merged PRs in 30d
Description
Use cases:
- Ride sharing where total not yet known.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Payment Request API specification and the discussion on this issue, focusing on how totals are currently represented and required. Done would require an agreed direction for supporting cases such as ride sharing where the total is not yet known, followed by the corresponding standard change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- api, payments
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100