Avoid syntax errors on oddly named fields.

dart/tests/html/track_element_constructor_test.dart

+// Copyright (c) 2013, the Dart project authors.  Please see the AUTHORS file
+// for details. All rights reserved. Use of this source code is governed by a
+// BSD-style license that can be found in the LICENSE file.
+
+// A regression test for dart2js generating illegal JavaScript code
+// dynamically in non-csp mode.  The name of the field "defaultValue"
+// in JavaScript is "default".  This meant that dart2js would create a
+// constructor function that looked like this:
+//
+// function TrackElement(default) { this.default = default; }
+
+import 'dart:html';
+
+void main() {
+  document.body.append(new TrackElement()..defaultValue = true);
+  if (!document.query('track').defaultValue) {
+    throw 'Expected default value to be true';

[sra1, 2013/05/16 00:09:31]

All the other tests under tests/html use the unit test framework.

I would suggest either
(1) change this to the unit test framework
(2) move the test to dart2js_native and construct a test case that has fields
named with all the keywords.

I think for (2) to be useful we would need to make sure the native tests are run
on all the browsers.  I'm not sure we do that.

[ahe, 2013/05/16 12:41:56]

I've added a test to dart2js_native that is much more extensive.

Unfortunately, test failures from pkg:unittest tests are really hard to debug
when you're working on compilers, so I prefer to avoid the framework when
testing the platform.

+  }
+  document.query('track').defaultValue = false;
+  if (document.query('track').defaultValue) {
+    throw 'Expected default value to be false';
+  }
+}