Re: [payment-request-tests] Test same origin-domain for BC containers and allowpaymentrequest (#4615)

# Chrome (unstable channel) #
Testing web-platform-tests at revision 15c541eebd1c904e7495658bceb03459205c6b5e
Using browser at version 55.0.2883.75
Starting 10 test iterations
All results were stable

## All results ##

<details>

<summary><a href="https://w3c-test.org/submissions/4615/payment-request/allowpaymentrequest/setting-allowpaymentrequest-timing.https.sub.html">/payment-request/allowpaymentrequest/setting-allowpaymentrequest-timing.https.sub.html</a></summary>


|                                        Subtest                                        | Results |
|---------------------------------------------------------------------------------------|---------|
|                                                                                       | ERROR   |
| `PaymentRequest setting allowpaymentrequest after document creation, before response` | FAIL    |

</details>

<details>

<summary><a href="https://w3c-test.org/submissions/4615/payment-request/allowpaymentrequest/allowpaymentrequest-attribute-cross-origin-bc-containers.https.html">/payment-request/allowpaymentrequest/allowpaymentrequest-attribute-cross-origin-bc-containers.https.html</a></summary>


| Subtest  | Results |
|----------|---------|
|          | ERROR   |
| `frame`  | FAIL    |
| `object` | FAIL    |
| `embed`  | FAIL    |
| `iframe` | FAIL    |

</details>

<details>

<summary><a href="https://w3c-test.org/submissions/4615/payment-request/allowpaymentrequest/no-attribute-same-origin-bc-containers.https.html">/payment-request/allowpaymentrequest/no-attribute-same-origin-bc-containers.https.html</a></summary>


| Subtest  | Results |
|----------|---------|
|          | ERROR   |
| `frame`  | FAIL    |
| `object` | FAIL    |
| `embed`  | FAIL    |
| `iframe` | FAIL    |

</details>

<details>

<summary><a href="https://w3c-test.org/submissions/4615/payment-request/allowpaymentrequest/no-attribute-cross-origin-bc-containers.https.html">/payment-request/allowpaymentrequest/no-attribute-cross-origin-bc-containers.https.html</a></summary>


| Subtest  | Results |
|----------|---------|
|          | ERROR   |
| `frame`  | FAIL    |
| `object` | FAIL    |
| `embed`  | FAIL    |
| `iframe` | FAIL    |

</details>

<details>

<summary><a href="https://w3c-test.org/submissions/4615/payment-request/allowpaymentrequest/allowpaymentrequest-attribute-same-origin-bc-containers.https.html">/payment-request/allowpaymentrequest/allowpaymentrequest-attribute-same-origin-bc-containers.https.html</a></summary>


| Subtest  | Results |
|----------|---------|
|          | ERROR   |
| `frame`  | FAIL    |
| `object` | FAIL    |
| `embed`  | FAIL    |
| `iframe` | FAIL    |

</details>

<details>

<summary><a href="https://w3c-test.org/submissions/4615/payment-request/allowpaymentrequest/removing-allowpaymentrequest.https.sub.html">/payment-request/allowpaymentrequest/removing-allowpaymentrequest.https.sub.html</a></summary>


|                                   Subtest                                    | Results |
|------------------------------------------------------------------------------|---------|
|                                                                              | ERROR   |
| `PaymentRequest removing allowpaymentrequest after load and then navigating` | FAIL    |

</details>

<details>

<summary><a href="https://w3c-test.org/submissions/4615/payment-request/allowpaymentrequest/setting-allowpaymentrequest.https.sub.html">/payment-request/allowpaymentrequest/setting-allowpaymentrequest.https.sub.html</a></summary>


|                                   Subtest                                   | Results |
|-----------------------------------------------------------------------------|---------|
|                                                                             | ERROR   |
| `PaymentRequest setting allowpaymentrequest after load and then navigating` | FAIL    |

</details>


View on GitHub: https://github.com/w3c/web-platform-tests/pull/4615#issuecomment-274825603

Received on Tuesday, 24 January 2017 17:17:01 UTC