Fix up DOM keyboardEvent constructor for dartium.

tests/html/keyboard_event_test.dart

 library KeyboardEventTest;
 import '../../pkg/unittest/lib/unittest.dart';
 import '../../pkg/unittest/lib/html_config.dart';
 import 'dart:html';
 
 // Test that we are correctly determining keyCode and charCode uniformly across
 // browsers.
 
 main() {
 
   useHtmlConfiguration();
 
   keydownHandlerTest(KeyEvent e) {
     expect(e.charCode, 0);
   }
 
+  test('keyboardEvent constructor', () {
+    var event = new KeyboardEvent('keyup', document.window);

[Emily Fortuna, 2012/12/07 18:29:05]

This is the one change that is different from the previous CL. I changed
"document.body" to "document.window"

Apparently webkit browsers are more forgiving and accept html elements as their
"view" but Firefox and IE want a proper Window.

+  });
   test('keys', () {
     // This test currently is pretty much a no-op because we
     // can't (right now) construct KeyboardEvents with specific keycode/charcode
     // values (a KeyboardEvent can be "init"-ed but not all the information can
     // be programmatically populated. It exists as an example for how to use
     // KeyboardEventController more than anything else.
     var controller = new KeyboardEventController.keydown(document.body);
     var func = keydownHandlerTest;
     controller.add(func);
     document.body.on.keyDown.add((e) => print('regular listener'), false);
   });
 }