Mon, 24 Oct 2011 13:30:37 -0600Rename nodeLength() to getNodeLength()
Aryeh Gregor <AryehGregor+gitcommit@gmail.com> [Mon, 24 Oct 2011 13:30:37 -0600] rev 646
Rename nodeLength() to getNodeLength()

nodeLength doesn't sound like a function name.

Mon, 24 Oct 2011 13:19:13 -0600Test isCollapsed
Aryeh Gregor <AryehGregor+gitcommit@gmail.com> [Mon, 24 Oct 2011 13:19:13 -0600] rev 645
Test isCollapsed

Tue, 11 Oct 2011 15:35:33 -0600Rename files for brevity
Aryeh Gregor <AryehGregor+gitcommit@gmail.com> [Tue, 11 Oct 2011 15:35:33 -0600] rev 644
Rename files for brevity

Tue, 11 Oct 2011 15:30:30 -0600Test collapseToStart/End properly
Aryeh Gregor <AryehGregor+gitcommit@gmail.com> [Tue, 11 Oct 2011 15:30:30 -0600] rev 643
Test collapseToStart/End properly

Results unsurprising: Gecko is perfect, WebKit is almost perfect except
that it doesn't support addRange() correctly, Opera is totally broken,
IE is basically okay and is correct per previous vague specs but has a
bug or two in light of the precise wording of the current spec.

Tue, 11 Oct 2011 13:20:52 -0600Cache results for normalizeColor/getLegacyFontSize
Aryeh Gregor <AryehGregor+gitcommit@gmail.com> [Tue, 11 Oct 2011 13:20:52 -0600] rev 642
Cache results for normalizeColor/getLegacyFontSize

This gives a decent speedup to gentest.html in Chrome. I didn't measure
exactly, but these two functions were showing up high on profiles and
now they've vanished. The major remaining culprits are things like
movePreservingRanges and setSelectionValue for self, and for total,
things like deleteSelection, isVisible, and restoreStatesAndValues. Not
so trivial to fix.

Tue, 11 Oct 2011 12:57:09 -0600Update comment
Aryeh Gregor <AryehGregor+gitcommit@gmail.com> [Tue, 11 Oct 2011 12:57:09 -0600] rev 641
Update comment

Tue, 11 Oct 2011 12:41:30 -0600Update conformancetest/diff
Aryeh Gregor <AryehGregor+gitcommit@gmail.com> [Tue, 11 Oct 2011 12:41:30 -0600] rev 640
Update conformancetest/diff

Apparently another Firefox bug crept in somewhere that we want to
ignore.

Tue, 11 Oct 2011 12:32:54 -0600Don't restrict what ranges can be in selections
Aryeh Gregor <AryehGregor+gitcommit@gmail.com> [Tue, 11 Oct 2011 12:32:54 -0600] rev 639
Don't restrict what ranges can be in selections

See the added <div class=comments>. This wound up being untenable,
mostly because of range mutations. The simpler path is definitely to
just let them be anything, and only restrict user-created selections.

Tue, 11 Oct 2011 12:14:47 -0600Convert to DOM4-style exceptions
Aryeh Gregor <AryehGregor+gitcommit@gmail.com> [Tue, 11 Oct 2011 12:14:47 -0600] rev 638
Convert to DOM4-style exceptions

Tue, 11 Oct 2011 11:53:26 -0600Move comment to the right place
Aryeh Gregor <AryehGregor+gitcommit@gmail.com> [Tue, 11 Oct 2011 11:53:26 -0600] rev 637
Move comment to the right place