Re: Initial pass of WebVR 1.1 conformance tests (#5535) from Rafael Cintron on 2017-04-14 (public-web-platform-tests-notifications@w3.org from April 2017)

From: Rafael Cintron <web-platform-tests-notifications@w3.org>
Date: Fri, 14 Apr 2017 15:16:28 GMT
To: public-web-platform-tests-notifications@w3.org
Message-Id: <<web-platform-tests_issue_5535_1492182988013@w3.org>>

Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

---

*[webvr/frozenArray_activeVRDisplays.html, line 32 at r1](https://reviewable.io:443/reviews/w3c/web-platform-tests/5535#-KhacEuILlrAUkmngdcJ:-Khh0x2zKATinfFclMY9:bkt6v69) ([raw file](https://github.com/w3c/web-platform-tests/blob/1881c6ec7ac93e74305baea1a0c929a99b78069e/webvr/frozenArray_activeVRDisplays.html#L32)):*
<details><summary><i>Previously, daoshengmu (Daosheng Mu) wrote…</i></summary><blockquote>

This test looks good to me. I am just curious why you wanna verify the array is not frozen in WebVR test. That seems to be not related to the field of WebVR.
</blockquote></details>

The reason for the test is to verify the array returned from the API is truly Frozen and cannot have any elements add or removed.  

---


*Comments from [Reviewable](https://reviewable.io:443/reviews/w3c/web-platform-tests/5535)*
<!-- Sent from Reviewable.io -->


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

Received on Friday, 14 April 2017 15:16:45 UTC