While concurrent requestAutocomplete calls for the same window are not allowed, we should ensure that we can display tab-modal UI for different tabs concurrently. The conflict resolution strategy, if an update to the same profile is requested, would be to store the fields in the latest update overriding the values stored in the other tab. Note that we may also make the actual profile editing UI non-modal and application-global, on some or all platforms, but we need a mechanism to handle concurrency in any case.
Summary: Ensure the requestAutocomplete use interface can be displayed concurrently → Ensure the requestAutocomplete user interface can be displayed concurrently
4 years ago
No longer blocks: 1018317
Points: --- → 8
Whiteboard: p=8 [qa+] → [qa+]
requestAutocomplete was removed from the HTML specification and while the same may apply to the Payment Request API we don't have a meta bug for that yet it seems.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.