Move html events generation to domimpl.

tests/html/documentfragment_test.dart

Index: tests/html/documentfragment_test.dart
diff --git a/tests/html/documentfragment_test.dart b/tests/html/documentfragment_test.dart
index 6a025a84b215bd336d67c21e499299a4a7159576..c27b3b9f074f60591a4ee18b94d6ed026b3ddcaa 100644
--- a/tests/html/documentfragment_test.dart
+++ b/tests/html/documentfragment_test.dart
@@ -280,7 +280,7 @@ main() {
   // Just test that these methods don't throw errors
   test("no-op methods don't throw errors", () {
     var fragment = new DocumentFragment();
-    fragment.on.click.add((e) => null);
+    fragment.on['click'].add((e) => null);

[sra1, 2012/05/14 17:29:15]

Why does on.click. no longer work?

[podivilov, 2012/05/15 10:24:26]

It looks like DocumentFragment shouldn't declare on.* listeners since there's no
DocumentFragment.onfoo attributes in DOM API.
While technically it is an event target, there's probably no real life use case
when you need to add onclick listener on DocumentFragment, so I think we should
remove it from the API.
It's outside of current cl scope, so I reverted the test for now. Let's discuss
on today's meeting.

     fragment.blur();
     fragment.focus();
     fragment.click();