Revision c0a1bc68d7f463a0f7b8a318d3cdc2b56e2cc044 authored by jugglinmike on 16 August 2018, 10:59:38 UTC, committed by Geoffrey Sneddon on 16 August 2018, 10:59:38 UTC
By using the null byte as a separator between test names, the output of the `tests-affected` and `files-changed` commands can be made safe for programmatic usage.
1 parent f62d0d3
idbfactory_open4.htm
<!DOCTYPE html>
<title>IDBFactory.open() - new database has default version</title>
<link rel="author" title="Microsoft" href="http://www.microsoft.com">
<script src=/resources/testharness.js></script>
<script src=/resources/testharnessreport.js></script>
<script src=support.js></script>
<script>
var open_rq = createdb(async_test(), 'database_name');
open_rq.onupgradeneeded = function(e) {
assert_equals(e.target.result.version, 1, "db.version");
};
open_rq.onsuccess = function(e) {
assert_equals(e.target.result.version, 1, "db.version");
this.done();
};
</script>
<div id=log></div>
Computing file changes ...
