Subramanya Sastry 031602f525 Fixed/updated newline handling for <p> tags ... - More pieces are now simplified and all(?) newline handling is now centralized in the serializeToken function. - This commit fixes bugs in rt-ing some code snippets ---------- Ex 1: foo<p>bar</p>baz ---------- - This commit fixes bugs serializing VE generated html ---------- Ex 2: <p>foo</p><pre>bar</pre> ==> foo\n bar ---------- - But, this round of fixes introduces RT failures for certain code examples in parserTests.txt. In all these failing cases, inline text/html is embedded within a generated <p> tag during parsing. If these generated <p> tags can have a "gc:1" attribute added to them, we can properly serialize them to the original form. ---------- Ex 3: foo<pre>bar</pre> Parsed HTML: <p>foo</p><pre>bar</pre> ---------- Note how this parsed HTML is identical to what the VE outputs in Example 2 above. So, without the gc:1 attribute, we now have conflicting requirements on the example same HTML. This increases confidence in the correctness of my commit here. Change-Id: I86beadec91c445a7f8a6d36a639b406697daa0a2		2012-06-18 11:25:21 -07:00
..
jquery	Add TransactionProcessor tests, and fix TP to make them pass	2012-04-30 19:06:20 -07:00
parser	Fixed/updated newline handling for <p> tags	2012-06-18 11:25:21 -07:00
qunit	Updated QUnit	2012-03-09 21:50:24 +00:00
rangy
sandbox	OMG. We have typing, autocorrect and spellcheck working. (Still no IME and still may break cut/paste)	2012-06-13 21:46:29 -07:00
ve	Focus can now be set in slugs using showCursor or showSelection.	2012-05-24 13:18:30 -07:00
ve2	Actually fix getRange() this time. Hopefully.	2012-06-15 16:09:08 -07:00