https://bugzilla.wikimedia.org/show_bug.cgi?id=57469
Roan Kattouw <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from Roan Kattouw <[email protected]> --- (In reply to comment #2) > So, actually, this is a slightly different use case than what is currently > supported. > > Try entering any of the extension tags in VE and Review changes. Parsoid > escapes the ext-tag like text as long as VE sends them back to Parsoid as > text, > i.e. <p>Foo&ot;ref>Bar</ref>Baz</p>. I verified this behavior in my > local install of VE. This is similar to entering <div> or any other HTML tag > as > text in VE. If VE does not escape those tag strings to text, Parsoid will not > be able to escape them. > That's how it should work, but on current master I get: $ echo "<p><ref></p>" | node js/tests/parse.js --html2wt <ref> $ echo "<p><ref> <code><ref></code></p>" | node js/tests/parse.js --html2wt <ref> <code><ref></code> -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
