Last modified: 2014-04-16 18:51:45 UTC
This looks like it was caused by bug 50771. $ echo "<ul><li><ul><li>x</li></ul>ul>" | tests/parse.js --html2wt warning in enwiki:Main_Page: Incompatible constraints (merge): { a: { min: 0, max: 1 }, b: { min: 1, max: 2 }, min: 1, max: 1 } { a: { min: 0, max: 1 }, b: {}, min: 0, max: 0, constraintInfo: { onSOL: true, sepType: 'parent-child', nodeA: 'UL', nodeB: 'LI' } } { a: {}, b: { min: 1, max: 2 }, min: 1, max: 2 } ** x Without data-parsoid hints, I guess the space insertion is inevitable -- but we shouldn't be causing incompatible constraints errors.
Whoops, it should be: $ echo "<ul><li><ul><li>x</li></ul></li></ul>" | tests/parse.js --html2wt Weird cut-and-paste issue. But the output is accurate.
And note that the php parser generates: <li> x for * x and <li>x for *x So I don't the resolution of bug 50771 was correct. If VE wants a space before the list item by default, it should be generating a space as the first character inside the <li>.
