Enable Try Dart to run on IE11.

site/try/src/html_to_text.dart

Index: site/try/src/html_to_text.dart
===================================================================
--- site/try/src/html_to_text.dart	(revision 38416)
+++ site/try/src/html_to_text.dart	(working copy)
@@ -41,7 +41,7 @@
 int htmlToText(Node root,
                StringBuffer buffer,
                TrySelection selection,
-               {bool treatRootAsInline: false}) {
+               {bool treatRootAsInline: true}) {

[aam-me, 2014/07/21 01:38:28]

Reason for this change is that diagnostic messages are block elements in IE(IE
doesn't support shadow nodes). So '\n' are being inserted as you edit through
the diagnostic message.
I could not clearly see the use case for adding '\n'(copy/pasting rich-text
source code?). So I adjusted this as well as the test.

[ahe, 2014/07/21 08:16:00]

IIRC, this code is to support copy and paste from, for example, Google Docs in
Chrome.

I'm not sure about this change. We should have removed the diagnostics before
getting to this point.

I can't find the "adjusted test".

[aam-me, 2014/07/21 12:20:38]

Interesting. I will look into this.
Ah, forgot to upload changelist with updated
tests\try\web\paste_content_rewriting_test.dart.
Added the test now.

[aam-me, 2014/07/30 00:28:25]

htmlToText is invoked from normalizeMutationRecord function, which receives
mutation records. In IE mutation records come back with diagnostic spans. For
example, typing some invalid characters 'ajs' at the end of the line "void
main() { ajs" results

in IE: Single line change: <span class="lineNumber" dart-state="{"><span
style="color: rgb(126, 8, 84);"><b>void</b></span> <span style="color: rgb(0, 0,
0);">main</span><span style="color: rgb(0, 0, 0);">(</span><span style="color:
rgb(0, 0, 0);">)</span> <span style="color: rgb(0, 0, 0);">{</span> <span
style="color: rgb(0, 0, 0);"><a class="diagnostic">ajs<span style="font-weight:
normal;"><span try-dart-shadow-root=""><span class="alert alert-error"
style="font-weight: normal; display: block;"><span
try-dart-shadow-root="">Expected ';' after this.</span></span><span
class="alert" style="font-weight: normal; display: block;"><span
try-dart-shadow-root="">Cannot resolve
'aj'.</span></span></span></span></a></span>

in Chrome:
Single line change: <span dart-state="{" class="lineNumber"><span style="color:
rgb(126, 8, 84);"><b>void</b></span> <span style="color: rgb(0, 0,
0);">main</span><span style="color: rgb(0, 0, 0);">(</span><span style="color:
rgb(0, 0, 0);">)</span> <span style="color: rgb(0, 0, 0);">{</span> <span
style="color: rgb(0, 0, 0);">ajs</span>
</span> 

And in IE this diagnostic element:

"<span try-dart-shadow-root=\"\"><span class=\"alert alert-error\"
style=\"font-weight: normal; display: block;\"><span
try-dart-shadow-root=\"\">Expected ';' after this.</span></span><span
class=\"alert\" style=\"font-weight: normal; display: block;\"><span
try-dart-shadow-root=\"\">Cannot resolve 'ajsd'.</span></span></span>"

triggers 'buffer.write('\n');' at line 72 below. Which results in additional
newline character added after line "void main() { ajs".

[ahe, 2014/08/04 08:59:55]

I noticed something troublesome in normalizeMutationRecord: we store line
containing the change in normalizedNodes, but then when we normalize the node
afterwards, we operate directly on "node", not the line. I suspect that is
broken.

Also, if you take a look at walkNodes in walkNodes in shadow_root.dart, the
diagnostic element is supposed to be skipped because it has the attribute
"try-dart-shadow-root". So something else is wrong, the closure on line 46 isn't
supposed to be invoked with a diagnostic element. Could you debug this aspect
and see if there is a bug in walkNodes?

   int selectionOffset = -1;
   walkNodes(root, (Node node) {
     if (selection.anchorNode == node) {