Catrope dc646ff32c Track adjustments in DocumentSynchronizer and apply them to oldRange ... This is needed because oldRange is relative to the state of the model before any changes were made, but when we call selectNodes() it's gonna operate on a partially updated model tree. This is a genuine bug in DocumentSynchronizer proper, which means I owe the entire team lunch Change-Id: Ia6510de19df02e961c7f25fb8e7833abceb8d25b		2012-06-20 23:40:38 -07:00
..
annotations	Move ve2/ back to ve/	2012-06-19 18:20:28 -07:00
nodes	Move ve2/ back to ve/	2012-06-19 18:20:28 -07:00
ve.dm.Annotation.js	Move ve2/ back to ve/	2012-06-19 18:20:28 -07:00
ve.dm.AnnotationFactory.js	Move ve2/ back to ve/	2012-06-19 18:20:28 -07:00
ve.dm.BranchNode.js	Move ve2/ back to ve/	2012-06-19 18:20:28 -07:00
ve.dm.Converter.js	Typo fixes throughout the codebase	2012-06-20 16:01:02 -07:00
ve.dm.Document.js	Typo fixes throughout the codebase	2012-06-20 16:01:02 -07:00
ve.dm.DocumentSynchronizer.js	Track adjustments in DocumentSynchronizer and apply them to oldRange	2012-06-20 23:40:38 -07:00
ve.dm.js	Move ve2/ back to ve/	2012-06-19 18:20:28 -07:00
ve.dm.LeafNode.js	Move ve2/ back to ve/	2012-06-19 18:20:28 -07:00
ve.dm.Node.js	Move ve2/ back to ve/	2012-06-19 18:20:28 -07:00
ve.dm.NodeFactory.js	Move ve2/ back to ve/	2012-06-19 18:20:28 -07:00
ve.dm.Surface.js	Cleaned up selection and focus code for inspectors	2012-06-20 19:22:38 -07:00
ve.dm.Transaction.js	Document how to remove attributes	2012-06-20 18:40:24 -07:00
ve.dm.TransactionProcessor.js	Fix adjustment of newRange in TransactionProcessor	2012-06-20 23:37:55 -07:00