Rename mdv -> template_binding, remove experiemntal apis from dart:html

pkg/polymer/lib/src/declaration.dart

Index: pkg/polymer/lib/src/declaration.dart
diff --git a/pkg/polymer/lib/src/declaration.dart b/pkg/polymer/lib/src/declaration.dart
index 07c0dc4074e7d72c3ea424f4193585c3611ae143..76c6eda6731fc7ef74cd62d673fec6566862b6fc 100644
--- a/pkg/polymer/lib/src/declaration.dart
+++ b/pkg/polymer/lib/src/declaration.dart
@@ -68,8 +68,8 @@ class PolymerDeclaration extends HtmlElement {
   List<Element> get styles => _styles;
 
   DocumentFragment get templateContent {
-    final template = this.query('template');
-    return template != null ? template.content : null;
+    final template = this.querySelector('template');
+    return template != null ? templateBind(template).content : null;

[Siggi Cherem (dart-lang), 2013/10/23 01:41:11]

I've been thinking about what we discussed in person. Is there a way we could
include a comment in to alert users about the fact that they shouldn't use
template.content and use templateBind(template).content instead? Could this go
in the docs of TemplateELement.content?

[Jennifer Messerly, 2013/10/23 02:05:02]

using ".content" could be okay as long as you don't mix it with this package. I
like the idea of improving the docs tho. maybe we can do in a follow up (i'm not
very familiar with how to edit HTML docs)

   }
 
   /** Maps event names and their associated method in the element class. */
@@ -336,8 +336,8 @@ class PolymerDeclaration extends HtmlElement {
   }
 
   void accumulateTemplatedEvents(Element node, Set<String> events) {
-    if (node.localName == 'template' && node.content != null) {
-      accumulateChildEvents(node.content, events);
+    if (node.localName == 'template') {
+      accumulateChildEvents(templateBind(node).content, events);
     }
   }