- From: Peter Saint-Andre via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Feb 2024 18:37:11 +0000
- To: public-device-apis-log@w3.org
stpeter has just created a new issue for https://github.com/w3c/contact-picker: == Add latitude and longitude to PaymentAddress interface? == Would it make sense to add optional latitude and longitude fields to the PaymentAddress construct? I see at least two potential use cases: (1) Providing a location hint in cases where a navigation system can yield ambiguous results (this happens to me all the time at home - delivery drivers will end up 20 miles away at a street with the same name in the next county). (2) Providing an accurate location in parts of the world where things like street names aren't used (e.g., https://hackernoon.com/online-shopping-in-africa-doesnt-work-because-of-this-web-form-e4974a8d165a describes this kind of scenario). Please view or discuss this issue at https://github.com/w3c/contact-picker/issues/72 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 12 February 2024 18:37:14 UTC