Ed Sanders d4eef1b879 Fix range translation for surface fragments ... Remove all manual changes to SF ranges as these are not undoable. Instead change translate range to default to outer expand and build functionality around that behaviour never changing. As translate range is always outer I don't think we need to check for start and end crossing over? Added more undo tests to assert these selections are maintained properly, and added the test case to 'update' for when and undo point is overwritten. Insert content now results in a selection over the inserted content. Most usages were expecting this anyway and were followed up with an adjustRange(-length,0) which is no longer necessary. Noticed that the link inspector case was never being triggered as word boundary was always expanding to at least one char (mainly for Hanzi selection). This doesn't make much sense as single spaces get auto selected so removed this functionality. Split collapseRange out into collapseRangeToStart and collapseRangeToEnd as this may be required to get the old behaviour (range moves to end after insert). Change-Id: I3dc0b4d00d37bad1ca3076a69b41c5f0b3fa0570		2013-04-30 17:08:15 +01:00
..
ve.dm.ElementLinearData.test.js	Fix range translation for surface fragments	2013-04-30 17:08:15 +01:00
ve.dm.MetaLinearData.test.js	Store data in LinearData class with an index-value store for objects	2013-03-30 10:06:34 +00:00