Set event interface for Payment Request update events #1315
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The spec uses an indirect update algorithm for these events, which confuses the extraction logic. Now that the update events are back, the `PaymentRequestUpdateEvent` interface is no longer an exception to the rule: it is being used to fire events.
dontcallmedom
approved these changes
Aug 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The spec uses an indirect update algorithm for these events, which confuses the extraction logic.
Now that the update events are back, the
PaymentRequestUpdateEventinterface is no longer an exception to the rule: it is being used to fire events. @dontcallmedom, w3c/payment-request#991 can probably be closed as a result?