Trevor Parscal 264b97df7f There's no such thing as ghosts, just sneaky array references ... When a document is created, it should take it upon itself to make sure it has a new reference to the data using slice, not place this on the caller. Callers that do not use slice will often find strange and mysterious things going on and not know why. The real reason is that multiple documents sharing a reference to the same data array leads to seriously messed up behavior. Change-Id: Ic4e25fcd9bf3f41a805003520a8f38e2768f5dbf		2012-08-17 10:37:28 -07:00
..
annotations	Update LinkAnnotation for Parsoid href changes	2012-08-14 11:03:37 -07:00
nodes	Add ve.dm.BreakNode to represent <br>	2012-08-09 14:50:25 -07:00
ve.dm.Annotation.js	Puttin' em white-spacers where they aught'a be	2012-08-06 18:52:19 -07:00
ve.dm.AnnotationFactory.js	Puttin' em white-spacers where they aught'a be	2012-08-06 18:52:19 -07:00
ve.dm.BranchNode.js	Make use of new jshint options	2012-08-10 02:50:30 +02:00
ve.dm.Converter.js	Recognize annotation types with multiple slashes correctly	2012-08-13 18:22:31 -07:00
ve.dm.Document.js	There's no such thing as ghosts, just sneaky array references	2012-08-17 10:37:28 -07:00
ve.dm.DocumentSynchronizer.js	Clean up a few commas and some indentation	2012-08-10 16:49:14 -07:00
ve.dm.js	Removed some whitespace	2012-07-19 14:25:16 -07:00
ve.dm.LeafNode.js	Puttin' em white-spacers where they aught'a be	2012-08-06 18:52:19 -07:00
ve.dm.Node.js	Strip and preserve inner leading&trailing whitespace in the linear model	2012-08-10 17:23:53 -07:00
ve.dm.NodeFactory.js	After much research on error objects, native = good, custom = bad	2012-08-08 10:48:53 -07:00
ve.dm.Surface.js	Changed initial surface range to (0, 0)	2012-08-16 13:16:48 -07:00
ve.dm.SurfaceFragment.js	Merge "Added setSelection to ve.dm.Surface"	2012-08-14 18:56:19 +00:00
ve.dm.Transaction.js	Added isNoOp to ve.dm.Transaction	2012-08-10 15:35:48 -07:00
ve.dm.TransactionProcessor.js	Clean up a few commas and some indentation	2012-08-10 16:49:14 -07:00