I'm pretty sure the first test in payment-request/payment-request-constructor-thcrash.https.html is incorrect because duplicate items in `methodData` provided to `PaymentRequest` should throw a `RangeError` according to step 4.3.3 of <https://www.w3.org/TR/payment-request/#constructor>. The spec does mention in <https://www.w3.org/TR/payment-request/#conformance> > User agents _MAY_ impose implementation-specific limits on otherwise unconstrained inputs, e.g., to prevent denial of service attacks, to guard against running out of memory, or to work around platform-specific limitations. When an input exceeds implementation-specific limit, the user agent _MUST_ throw, or, in the context of a promise, reject with, a `TypeError` optionally informing the developer of how a particular input exceeded an implementation-specific limit. but does not specify whether this should happen before or after the above. In WebKit's case, there is no "implementation-specific limit", so WebKit shouldn't throw a `TypeError` regardless.
Created attachment 418158 [details] Patch
This patch modifies the imported WPT tests. Please ensure that any changes on the tests (not coming from a WPT import) are exported to WPT. Please see https://trac.webkit.org/wiki/WPTExportProcess
Created attachment 418161 [details] Patch
Created attachment 418162 [details] Patch
Created attachment 418163 [details] Patch
Created attachment 418172 [details] Patch
Created attachment 418173 [details] Patch
Submitted web-platform-tests pull request: https://github.com/web-platform-tests/wpt/pull/27292
Comment on attachment 418173 [details] Patch Let's r+ it again so that WPT bot gets it
Committed r271759: <https://trac.webkit.org/changeset/271759> All reviewed patches have been landed. Closing bug and clearing flags on attachment 418173 [details].
<rdar://problem/73514233>