If everything is OK, you can merge this pull request which will report the issue below to the repo, and update the underlying report file with a link to the said issue.
While crawling Payment Handler API, the following algorithms fire an event, or resolve or reject a Promise, within a step that runs in parallel without first queuing a task:
[ ] The algorithm that starts with "Upon receiving a PaymentRequest by way of PaymentRequest.show() and subsequent user selection of a payment handler, the user agent MUST run the following steps:" resolves/rejects a promise directly in a step that runs in parallel
[ ] An algorithm resolves/rejects a promise directly in a step that runs in parallel
See Dealing with the event loop in the HTML specification for guidance on how to deal with algorithm sections that run in parallel.
Cc @dontcallmedom @tidoust
This issue was detected and reported semi-automatically by Strudy based on data collected in webref.
This pull request was automatically created by Strudy upon detecting errors in Missing tasks in parallel steps in Payment Handler API.
Please check that these errors were correctly detected, and that they have not already been reported in https://github.com/w3c/payment-handler.
If everything is OK, you can merge this pull request which will report the issue below to the repo, and update the underlying report file with a link to the said issue.
Title: Missing tasks in parallel steps in Payment Handler API Tracked: N/A Repo: 'https://github.com/w3c/payment-handler'
While crawling Payment Handler API, the following algorithms fire an event, or resolve or reject a Promise, within a step that runs in parallel without first queuing a task:
See Dealing with the event loop in the HTML specification for guidance on how to deal with algorithm sections that run in parallel.
Cc @dontcallmedom @tidoust
This issue was detected and reported semi-automatically by Strudy based on data collected in webref.