Bring back initPolymer, allow boot.js only if using "polymer_experimental.html".

pkg/polymer/test/event_path_test.dart

Index: pkg/polymer/test/event_path_test.dart
diff --git a/pkg/polymer/test/event_path_test.dart b/pkg/polymer/test/event_path_test.dart
index ecf922f5ce9955d4bf8f475e2f0a622a77289de1..121b346788535065ad34f5db76971f74ebd24501 100644
--- a/pkg/polymer/test/event_path_test.dart
+++ b/pkg/polymer/test/event_path_test.dart
@@ -25,7 +25,6 @@ class XMenuButton extends PolymerElement {
   XMenuButton.created() : super.created();
 }
 
-@initMethod
 main() {
   // TODO(sigmund): use @CustomTag instead of Polymer.regsiter. A bug is making
   // this code sensitive to the order in which we register elements (e.g. if
@@ -35,6 +34,7 @@ main() {
   Polymer.register('x-menu', XMenu);
   Polymer.register('x-menu-button', XMenuButton);
 
+  initPolymer();

[Jennifer Messerly, 2014/05/23 07:20:06]

hmmm, I wonder if this should be sooner? Not sure the use case of initPolymer
after Polymer.register ... but it is interesting that it works :). I'm guessing
we had this previously? I wonder if it was on purpose.

[Siggi Cherem (dart-lang), 2014/05/23 17:56:33]

good catch. I am as curious. It seems to be working fine moving this to the top,
so I did.

   useHtmlConfiguration();
 
   setUp(() => Polymer.onReady);