Catrope 031b96dd2a Make metadata reaping handle replacement operations more sanely ... Before, replacement operations that both inserted and removed data at the same time would be treated as removals followed by insertions, so we'd reap the metadata from the affected range and move it to the start of the range. For a pure replacement, this doesn't make any sense. Instead, preserve the first min(insertLength, removeLength) elements in the metadata array, then perform a pure insertion splice or a pure removal splice for the length adjustment. Any metadata reaped in a removal splice is restored at the offset where we started removing, after the preserved portion. These changes make the behavior of metadata reaping saner in general (the previous behavior had the potential to move metadata around if it was near a paragraph opening or closing and you converted the paragraph to a heading), and makes the behavior match up with translateOffset(), which is desirable for MetaList synchronization. Change-Id: If9a1c6a7cf43ead7e3e1e8f6e081b139ca65fa53		2013-03-14 23:35:50 -07:00
..
jquery	Removed code for and links to unused libraries	2013-01-10 13:25:33 -08:00
qunit	Upstream: Update QUnit from v1.10.0 to v1.11.0	2013-02-19 19:50:02 +01:00
rangy
ve	Make metadata reaping handle replacement operations more sanely	2013-03-14 23:35:50 -07:00