Getting html_dart2js and html_dartium a bit more in sync.

tools/dom/templates/html/impl/impl_Element.darttemplate

Index: tools/dom/templates/html/impl/impl_Element.darttemplate
diff --git a/tools/dom/templates/html/impl/impl_Element.darttemplate b/tools/dom/templates/html/impl/impl_Element.darttemplate
index e4faf0ceb80daa8267c5bc0bd2213b8198ae2e23..18b6cf82d494adf4240bff08f68c27ac7f54f221 100644
--- a/tools/dom/templates/html/impl/impl_Element.darttemplate
+++ b/tools/dom/templates/html/impl/impl_Element.darttemplate
@@ -553,11 +553,11 @@ $if DART2JS
    * * [insertAdjacentText]
    * * [insertAdjacentElement]
    */
-  void insertAdjacentHtml(String where, String text) {
+  void insertAdjacentHtml(String where, String html) {

[Emily Fortuna, 2013/05/14 00:29:30]

really? the analyzer cares about parameter names? Okay.

[blois, 2013/05/14 01:03:16]

It's a different one that I made using the analyzer_experimental library-
https://codereview.chromium.org/14750010/ (can't submit because it relies on
patches to the analyzer).

But in general it seems like 'goodness' to have our members all named the same-
ensures the docs make sense.

     if (JS('bool', '!!#.insertAdjacentHtml', this)) {
-      _insertAdjacentHtml(where, text);
+      _insertAdjacentHtml(where, html);
     } else {
-      _insertAdjacentNode(where, new DocumentFragment.html(text));
+      _insertAdjacentNode(where, new DocumentFragment.html(html));
     }
   }