| Index: conformance/array-buffer-crash.html
|
| ===================================================================
|
| --- conformance/array-buffer-crash.html (revision 106149)
|
| +++ conformance/array-buffer-crash.html (working copy)
|
| @@ -1,38 +0,0 @@
|
| -<!--
|
| -Copyright (c) 2011 The Chromium Authors. All rights reserved.
|
| -Use of this source code is governed by a BSD-style license that can be
|
| -found in the LICENSE file.
|
| - -->
|
| -<html>
|
| -<head>
|
| -<meta charset="utf-8">
|
| -<link rel="stylesheet" href="../resources/js-test-style.css"/>
|
| -<script src="../resources/js-test-pre.js"></script>
|
| -<script src="resources/webgl-test.js"></script>
|
| -</head>
|
| -<body>
|
| -<div id="description"></div>
|
| -<div id="console"></div>
|
| -
|
| -<script>
|
| -
|
| -description('Test ArrayBuffer.byteLength');
|
| -
|
| -// The following used to cause a crash in Chrome.
|
| -
|
| -// Note that because the argument to ArrayBuffer's constructor is not
|
| -// optional, an implementation might throw an exception on the expression
|
| -// below rather than implicitly passing undefined. Either way is acceptable
|
| -// from the point of view of this test, but implementations must not crash.
|
| -try {
|
| - new ArrayBuffer().byteLength;
|
| -} catch (e) {
|
| -}
|
| -
|
| -testPassed("new ArrayBuffer().byteLength did not crash");
|
| -successfullyParsed = true;
|
| -
|
| -</script>
|
| -<script src="../resources/js-test-post.js"></script>
|
| -</body>
|
| -</html>
|
|
|