Steps towards handling `new Element.div()`

tests/compiler/dart2js/kernel/compile_from_dill_test_helper.dart

Index: tests/compiler/dart2js/kernel/compile_from_dill_test_helper.dart
diff --git a/tests/compiler/dart2js/kernel/compile_from_dill_test_helper.dart b/tests/compiler/dart2js/kernel/compile_from_dill_test_helper.dart
index b934b660ac82c23954b78346549ffc3cc05e2286..a74a58d08f9a2f9cd5a2ca5ce910192707c5c270 100644
--- a/tests/compiler/dart2js/kernel/compile_from_dill_test_helper.dart
+++ b/tests/compiler/dart2js/kernel/compile_from_dill_test_helper.dart
@@ -31,6 +31,8 @@ import 'compiler_helper.dart';
 
 const SOURCE = const {
   'main.dart': '''
+import 'dart:html';
+
 foo({named}) => 1;
 bar(a) => !a;
 class Class {
@@ -42,12 +44,15 @@ class Class {
 
   method() {}
 }
-
+ 
 class SubClass extends Class {
   method() {
     super.method();
   }  
 }
+
+var toplevel;

[Siggi Cherem (dart-lang), 2017/06/27 20:20:43]

This seems a bit unrelated to the change, is it related? or just a separate test
for top-levels fields?

[Johnni Winther, 2017/06/28 08:09:05]

It was on the path - triggering the fix in element_map_impl.

+
 main() {
   foo();
   bar(true);
@@ -80,6 +85,7 @@ main() {
     x = v;
     if (v == 5) break;
   }
+  x = toplevel;
   print(x);
   return x;
 }