Ed Sanders 42f82cf15f Include element HTML in QUnit summary for diff ... Because trying to work out how broken your test case is by looking at two (potentially multi-page) serialisations of the DOM summary is a pain in the arse. Diffing two HTML strings may highlight the problem much more clearly. TODO: Is it possible to defer the calculation of the HTML infused summary object until we have determined the assertion has failed. Otherwise we're slowing down our tests for no reason. Change-Id: I873bf2479ab81d15389792bd59d15580da63941a		2013-08-02 16:10:05 +01:00
..
ce	doc: @return -> @returns	2013-08-01 02:10:23 +02:00
dm	doc: @return -> @returns	2013-08-01 02:10:23 +02:00
init	Merge "Language Inspector UI"	2013-07-31 07:14:56 +00:00
test	Include element HTML in QUnit summary for diff	2013-08-02 16:10:05 +01:00
ui	Expand beta message a bit.	2013-08-01 21:45:53 -07:00
ve.BranchNode.js
ve.debug.js
ve.Document.js	doc: Clean up spacing that caused <pre> or broken <ul>/<ol>	2013-07-25 04:02:50 +02:00
ve.Element.js	ve.ui.Toolbar: Refactor floating logic for performance	2013-07-30 01:47:54 +02:00
ve.EventEmitter.js
ve.Factory.js
ve.js	Include element HTML in QUnit summary for diff	2013-08-02 16:10:05 +01:00
ve.LeafNode.js
ve.NamedClassFactory.js
ve.Node.js
ve.Range.js
ve.Registry.js