https://bugzilla.wikimedia.org/show_bug.cgi?id=57469
--- Comment #2 from [email protected] --- 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. Currently, Domino parses "<ref>foo</ref>" as a valid XML tree which is the same behavior as the browser (verified in the web console). So, while Parsoid could check the node name against the set of valid HTML5 tags and nowiki the others (since we are not serializing a generic XML domtree), why would VE not entity-escape "<" and ">" chars entered as text before sending them to Parsoid, i.e. is this a valid use case in the context of VE editing? -- 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
